This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [Patch] Mark the thread_event breakpoint as "not inserted" before calling thread_mourn_inferior
- From: Daniel Jacobowitz <drow at false dot org>
- To: Girish Shilamkar <girish at linsyssoft dot com>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Tue, 17 Jan 2006 10:40:04 -0500
- Subject: Re: [Patch] Mark the thread_event breakpoint as "not inserted" before calling thread_mourn_inferior
- References: <1137512294.3217.29.camel@krypton>
On Tue, Jan 17, 2006 at 09:08:14PM +0530, Girish Shilamkar wrote:
> This problem occurs since gdb tries to remove thread_event breakpoint
> after the thread has exited and tries to read the address space since
> the breakpoint is still marked as updated.
> In the attached patch we mark the thread_event breakpoint as "not
> inserted" before calling thread_mourn_inferior.
> Is this the right way?
Definitely not. We need more information about this bug: what do you
do to reproduce it, since no one else has encountered it?
--
Daniel Jacobowitz
CodeSourcery