This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Faster stepping amidst breakpoints
- From: Daniel Jacobowitz <dan at codesourcery dot com>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: Maxim Grigoriev <maxim at tensilica dot com>, "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>, Marc Gauthier <marc at tensilica dot com>, Pedro Alves <pedro at codesourcery dot com>, Stan Shebs <stan at codesourcery dot com>
- Date: Mon, 31 Jan 2011 10:12:35 -0500
- Subject: Re: Faster stepping amidst breakpoints
- References: <4D3A114D.7010301@tensilica.com> <20110123001433.GA6352@caradoc.them.org> <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