This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [Cygwin] Fix for: detaching crashes the inferior.


On 4/9/07, Eli Zaretskii <eliz@gnu.org> wrote:
> Date: Mon, 09 Apr 2007 03:06:20 +0100
> From: Pedro Alves <pedro_alves@portugalmail.pt>
>
> Is there a case where we can get to to_detach
> without remove_breakpoints being called?  I don't think there
> is - we always get here through normal_stop, right?

If you think this must be so, but are unsure, you can add a flag that
is turned off in remove_breakpoints and turned on when a breakpoint is
set.  Then, in to_detach, if the flag is on, you can scream bloody
murder (and even abort(), if you think it's fatal).  Once users start
using the modified version, you will soon know whether the assumption
was wrong...


:) Thanks for the hint, I'll try to do that.


I think that gdb by design always removes the breakpoints from the
inferior when it stops, but it would be nice if someone would confirm
or unconfirm this.

Cheers,
Pedro Alves


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]