From: Daniel Jacobowitz <drow@false.org>
To: Girish Shilamkar <girish@linsyssoft.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [Patch] Mark the thread_event breakpoint as "not inserted" before calling thread_mourn_inferior
Date: Tue, 17 Jan 2006 15:40:00 -0000 [thread overview]
Message-ID: <20060117154004.GA3672@nevyn.them.org> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2006-01-17 15:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 15:35 Girish Shilamkar
2006-01-17 15:40 ` Daniel Jacobowitz [this message]
2006-01-18 9:11 ` Girish Shilamkar
2006-01-18 13:57 ` Daniel Jacobowitz
2006-01-20 14:14 ` Girish Shilamkar
2006-01-20 14:35 ` Daniel Jacobowitz
2006-01-23 9:21 ` Girish Shilamkar
2006-01-24 21:52 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060117154004.GA3672@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=girish@linsyssoft.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox