From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31244 invoked by alias); 13 Jan 2002 08:31:38 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 31211 invoked from network); 13 Jan 2002 08:31:37 -0000 Received: from unknown (HELO is.elta.co.il) (199.203.121.2) by sources.redhat.com with SMTP; 13 Jan 2002 08:31:37 -0000 Received: from is (is [199.203.121.2]) by is.elta.co.il (8.9.3/8.8.8) with SMTP id KAA07089; Sun, 13 Jan 2002 10:30:38 +0200 (IST) Date: Sun, 13 Jan 2002 00:31:00 -0000 From: Eli Zaretskii X-Sender: eliz@is To: Mark Kettenis cc: Pierre Muller , gdb-patches@sources.redhat.com Subject: Re: [RFA/RFC 3] Remove hardware break and watchpoints at program exit. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-01/txt/msg00339.txt.bz2 On 12 Jan 2002, Mark Kettenis wrote: > Those functions shouldn't be called when there is no debuggee. I > suspect that there is something wrong with the hardware > breakpoint/watchpoint implementation at a much higher level. The problem, IMHO, is that GDB's application level doesn't tell the target-specific low-end that it's time to clean up the watchpoint related data structures. The DJGPP port uses mourn_inferior to do that, but this might not be a good general solution, especially since so many popular targets use the generic version of mourning. I think we need to have code that explicitly cleans up watchpoints when the debuggee exits.