This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Faster stepping amidst breakpoints
- From: Joel Brobecker <brobecker at adacore dot com>
- To: "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
- Date: Tue, 1 Feb 2011 07:23:38 +0400
- Subject: Re: Faster stepping amidst breakpoints
- References: <4D3A114D.7010301@tensilica.com> <20110123001433.GA6352@caradoc.them.org> <20110131044951.GG2384@adacore.com> <20110131151229.GA2915@caradoc.them.org>
> 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.
I see this as an acceptable outcome of a debugger crash. I am guessing
that in most cases, people debug their program, and then want it killed,
so leaving the inferior behind with breakpoints inserted won't matter
much (or, not as much as having their session brutally interrupted by
the crash itself). For the small number of those for whom it matters,
they can change the switch back...
I was more worried about possible issues during normal operations.
For instance, has this been tested with software-single-step, for
instance? What I'm going to do, to give it a little more exposure,
is flip the switch in AdaCore's HEAD build, and monitor the testsuite
results. Have you flipped the switch in CS's builds too?
--
Joel