From: Daniel Jacobowitz <dan@codesourcery.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Maxim Grigoriev <maxim@tensilica.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Marc Gauthier <marc@tensilica.com>,
Pedro Alves <pedro@codesourcery.com>,
Stan Shebs <stan@codesourcery.com>
Subject: Re: Faster stepping amidst breakpoints
Date: Mon, 31 Jan 2011 15:39:00 -0000 [thread overview]
Message-ID: <20110131151229.GA2915@caradoc.them.org> (raw)
In-Reply-To: <20110131044951.GG2384@adacore.com>
On Mon, Jan 31, 2011 at 08:49:51AM +0400, Joel Brobecker wrote:
> > Consider "set breakpoint always-inserted".
> > I've been wondering lately if we should flip the default.
>
> I like the idea of changing the default.
>
> Do you know what the risks would be? I looked at the code, and
> there isn't something obvious/delicate, it seems. Perhaps we might
> find ourselves forgetting to re-insert breakpoints, or inserting
> them twice? I think you guys have more experience than we do?
As far as I can remember (you know how much GDB development I do
nowadays), the only risks were if GDB crashed and left the application
with breakpoints inserted. Of course, I'm in favor of GDB not
crashing.
Pedro, Stan, any thoughts?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2011-01-31 15:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-22 15:06 Maxim Grigoriev
2011-01-24 8:04 ` Daniel Jacobowitz
2011-01-24 21:08 ` Maxim Grigoriev
2011-01-31 7:47 ` Joel Brobecker
2011-01-31 15:39 ` Daniel Jacobowitz [this message]
2011-02-01 3:23 ` Joel Brobecker
2011-02-01 18:44 ` Michael Snyder
2011-02-03 4:55 ` Joel Brobecker
2011-02-02 17:10 ` Daniel Jacobowitz
2011-02-03 4:46 ` Joel Brobecker
2011-02-13 15:17 ` Mark Kettenis
2011-02-14 3:27 ` Joel Brobecker
2011-02-14 10:50 ` Joel Brobecker
2011-02-01 15:12 ` Pedro Alves
2011-02-03 22:54 ` Maxim Grigoriev
2011-02-04 16:06 ` Tom Tromey
2011-02-04 19:32 ` Maxim Grigoriev
2011-02-04 16:33 ` Daniel Jacobowitz
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=20110131151229.GA2915@caradoc.them.org \
--to=dan@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=marc@tensilica.com \
--cc=maxim@tensilica.com \
--cc=pedro@codesourcery.com \
--cc=stan@codesourcery.com \
/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