From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16803 invoked by alias); 28 Mar 2005 22:40:31 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 16576 invoked from network); 28 Mar 2005 22:40:03 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 28 Mar 2005 22:40:03 -0000 Received: from drow by nevyn.them.org with local (Exim 4.50 #1 (Debian)) id 1DG2ur-0000Dy-Ux for ; Mon, 28 Mar 2005 17:41:02 -0500 Date: Mon, 28 Mar 2005 22:40:00 -0000 From: Daniel Jacobowitz To: GDB Subject: Re: [mi] watchpoint-scope exec async command Message-ID: <20050328224101.GA629@nevyn.them.org> Mail-Followup-To: GDB References: <20050325161239.GA12231@white> <01c53207$Blat.v2.4$3def9b00@zahav.net.il> <20050328225619.GB3413@white> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050328225619.GB3413@white> User-Agent: Mutt/1.5.6+20040907i X-SW-Source: 2005-03/txt/msg00263.txt.bz2 On Mon, Mar 28, 2005 at 05:56:19PM -0500, Bob Rossi wrote: > (gdb) n > Hardware watchpoint 2 deleted because the program has left the block > in which its expression is valid. > Segmentation fault > > The crash only happens sometimes. Although when I run it over and over, > I will eventually get it. > > Here is the problem I found, > > (gdb) n > Hardware watchpoint 2 deleted because the program has left the block > in which its expression is valid. > ==26644== Invalid write of size 4 > ==26644== at 0x80D9B32: insert_bp_location (breakpoint.c:1022) > ==26644== by 0x80D9EDA: insert_breakpoints (breakpoint.c:1151) > ==26644== by 0x8119620: proceed (infrun.c:774) I envy you. I can't get valgrind to work with GDB; once I try to run a child process, it falls over. > So, basically, I can't figure out why the breakpoint field > 'related_breakpoint' became in valid. I believe it was valid when the > breakpoint was created, since the memset is there. However, at some > point, it must have become invalid ... The related breakpoint is supposed to be the scope breakpoint; I can't see how they could become unpaired. You may want to run a debugger on GDB, using a watchpoint to see what changes it? -- Daniel Jacobowitz CodeSourcery, LLC