This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Faster stepping amidst breakpoints
- From: Mark Kettenis <mark dot kettenis at xs4all dot nl>
- To: brobecker at adacore dot com
- Cc: gdb-patches at sourceware dot org
- Date: Sun, 13 Feb 2011 16:16:44 +0100 (CET)
- 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> <20110201032338.GI2384@adacore.com>
> Date: Tue, 1 Feb 2011 07:23:38 +0400
> From: Joel Brobecker <brobecker@adacore.com>
>
> > 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...
You're probably right for the case where people start the program from
GDB, but I guess that when people attach to an already running process
they typically don't want to kill it when they're done with debugging.
That said, it is probably a bad idea to have different behaviour for
"run" and "attach" in this case. Let's throw the switch after the 7.3
release and see if people even notice.