From: Joel Brobecker <brobecker@adacore.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Support temporary breakpoints in runto_main.
Date: Wed, 22 May 2013 04:47:00 -0000 [thread overview]
Message-ID: <20130522044646.GY4017@adacore.com> (raw)
In-Reply-To: <yjt2obc3c06n.fsf@ruffy2.mtv.corp.google.com>
> If I imagine I'm new to gdb and see the name runto_main I can well
> imagine not expecting the implementation of that command to leave the
> breakpoint behind. Leaving the breakpoint behind is not something I
> would expect from that name.
FWIW, the AdaCore's gdb-testsuite framework defines a "runto" method,
and it does set a temporary breakpoint by default (with the option
of making it permanent). Same reasoning as yours went into the "design"
of this method's interface.
Not sure if it's worth spending time changing this, but I would
welcome the change...
--
Joel
next prev parent reply other threads:[~2013-05-22 4:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 0:45 Doug Evans
2013-05-22 4:47 ` Joel Brobecker [this message]
2013-05-22 7:34 ` Doug Evans
2013-05-22 10:04 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130522044646.GY4017@adacore.com \
--to=brobecker@adacore.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox