From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27322 invoked by alias); 8 Oct 2008 22:24:55 -0000 Received: (qmail 27312 invoked by uid 22791); 8 Oct 2008 22:24:54 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 08 Oct 2008 22:24:19 +0000 Received: (qmail 27085 invoked from network); 8 Oct 2008 22:24:18 -0000 Received: from unknown (HELO orlando.local) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 8 Oct 2008 22:24:18 -0000 From: Pedro Alves To: gdb@sourceware.org Subject: Re: Detaching from a remote progam: Why does GDB retain breakpoints? Date: Wed, 08 Oct 2008 22:24:00 -0000 User-Agent: KMail/1.9.9 Cc: "Anmol P. Paralkar" References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200810082324.17293.pedro@codesourcery.com> X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-10/txt/msg00030.txt.bz2 On Wednesday 08 October 2008 23:01:57, Anmol P. Paralkar wrote: > I am trying to understand the 'detach' command and need your help. > > The documentation says: > > "After the detach command, gdb is free to connect to another target." > > So, why does GDB retain breakpoints after detaching from the remote target? GDB shouldn't be leaving breakpoints installed in the target on a detach. If it is, it is a bug. If you refering to breakpoints as what is listed by "info breakpoints", we just keep them, well, that's a user interface issue. We leave them because we can, it can be useful. Just like we keep breakpoint if the program just exits normally after a "run". > The documentation for 'disconnect' indicates that GDB could possibly re-connect > to the same remote target so I can see why it makes sense to retain breakpoints > on a 'disconnect'. But, with a 'detach', a D-packet is sent and I suppose stubs > will then typically relinquish control and have the target proper take over. > > Should'nt GDB clear out all its target related debug-state on a 'detach'? > You should be seeing GDB removing the breakpoints from the target before you see the 'D' packet: either with `z' packets if the stub supports them, or memory writes otherwise. Is this what you meant? -- Pedro Alves