From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1184 invoked by alias); 10 Sep 2004 15:18:46 -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 1170 invoked from network); 10 Sep 2004 15:18:45 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 10 Sep 2004 15:18:45 -0000 Received: from drow by nevyn.them.org with local (Exim 4.34 #1 (Debian)) id 1C5nAY-0000bG-GB; Fri, 10 Sep 2004 11:18:34 -0400 Date: Fri, 10 Sep 2004 15:18:00 -0000 From: Daniel Jacobowitz To: Fabian Cenedese Cc: gdb@sources.redhat.com Subject: Re: Auto removing BPs on stop Message-ID: <20040910151834.GB2103@nevyn.them.org> Mail-Followup-To: Fabian Cenedese , gdb@sources.redhat.com References: <5.2.0.9.1.20040910135924.01d27220@NT_SERVER> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5.2.0.9.1.20040910135924.01d27220@NT_SERVER> User-Agent: Mutt/1.5.5.1+cvs20040105i X-SW-Source: 2004-09/txt/msg00082.txt.bz2 On Fri, Sep 10, 2004 at 02:08:16PM +0200, Fabian Cenedese wrote: > Hi > > Whenever the target stops gdb will remove all breakpoints from the target > and set them again before stepping/continuing. What functionality in gdb > depends on this? Backtrace? Breakpoint handling? > In our multitasking system a thread can stop on a breakpoint while the > others are still running, so the breakpoints are still useful and shouldn't > be removed. GDB can't cope with this. GDB assumes that when it is told that the inferior has "stopped", its state will not change, and all threads can be examined. > What would break in gdb if I just removed those calls to unset/re-set > the breakpoints? I know that the setting is partly necessary as new > breakpoints aren't yet set. I don't know. A lot of places may still read target memory without using the routines that "remove" breakpoints from GDB's image of target memory, for one thing; this is slowly being fixed. My goal is to stop the needless removing and reinserting some day, but I don't think it will work yet. -- Daniel Jacobowitz