From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16539 invoked by alias); 17 Jan 2006 15:40:07 -0000 Received: (qmail 16525 invoked by uid 22791); 17 Jan 2006 15:40:06 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Tue, 17 Jan 2006 15:40:06 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1EyswG-0000xt-8W; Tue, 17 Jan 2006 10:40:04 -0500 Date: Tue, 17 Jan 2006 15:40:00 -0000 From: Daniel Jacobowitz To: Girish Shilamkar Cc: gdb-patches@sources.redhat.com Subject: Re: [Patch] Mark the thread_event breakpoint as "not inserted" before calling thread_mourn_inferior Message-ID: <20060117154004.GA3672@nevyn.them.org> Mail-Followup-To: Girish Shilamkar , gdb-patches@sources.redhat.com References: <1137512294.3217.29.camel@krypton> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1137512294.3217.29.camel@krypton> User-Agent: Mutt/1.5.8i X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-01/txt/msg00217.txt.bz2 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