From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19949 invoked by alias); 11 Mar 2005 01:28:08 -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 19930 invoked from network); 11 Mar 2005 01:28:05 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 11 Mar 2005 01:28:05 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id j2B1S4qH030462 for ; Thu, 10 Mar 2005 20:28:05 -0500 Received: from opsy.redhat.com (vpn50-11.rdu.redhat.com [172.16.50.11]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id j2B1S3n15237; Thu, 10 Mar 2005 20:28:03 -0500 Received: by opsy.redhat.com (Postfix, from userid 500) id D514D2DD3B0; Thu, 10 Mar 2005 18:25:30 -0700 (MST) To: RT Cc: "'Atul Talesara'" , "'Hareesh Nagarajan'" , "'GDB'" Subject: Re: Is it possible to save breakpoints to a file? References: <423070F6.40500@dsl.pipex.com> From: Tom Tromey Reply-To: tromey@redhat.com X-Attribution: Tom Date: Fri, 11 Mar 2005 01:28:00 -0000 In-Reply-To: <423070F6.40500@dsl.pipex.com> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2005-03/txt/msg00122.txt.bz2 >>>>> "RT" == RT writes: >> If you are using the insight GUI for gdb, that will save your breakpoints >> for you as part of the project preferences. It writes them into .gdbinit >> automatically and reloads them next time you're debugging the same >> executable. RT> Which makes life rather difficult if you have a break set in a shared RT> library. If you reply 'yes' by mistake when Insight asks if you want RT> to make the break pending on the library load, then gdb will rapidly RT> crash. I don't know if this is in the gdb bug database; it should be. More importantly, Insight should probably automatically set all restored breakpoints to be pending breakpoints as needed, without asking the user. Presumably if they were saved, then they once existed. Making them pending seems like a UI improvement without much downside. (You might carry stale pending breakpoints around, say if you delete a function that had a breakpoint in it. But you probably also won't care.) Tom