From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12387 invoked by alias); 12 Mar 2005 11:58:29 -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 12171 invoked from network); 12 Mar 2005 11:58:11 -0000 Received: from unknown (HELO mail.netspace.net.au) (203.10.110.76) by sourceware.org with SMTP; 12 Mar 2005 11:58:11 -0000 Received: from [192.168.1.11] (220-253-28-118.VIC.netspace.net.au [220.253.28.118]) by mail.netspace.net.au (Postfix) with ESMTP id 251C710CA47 for ; Sat, 12 Mar 2005 22:58:09 +1100 (EST) Message-ID: <4232D9B3.9030900@netspace.net.au> Date: Sat, 12 Mar 2005 11:58:00 -0000 From: Russell Shaw User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050105 Debian/1.7.5-1 MIME-Version: 1.0 Cc: 'GDB' Subject: Re: Is it possible to save breakpoints to a file? References: <423070F6.40500@dsl.pipex.com> <4232D267.10303@dsl.pipex.com> In-Reply-To: <4232D267.10303@dsl.pipex.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-03/txt/msg00137.txt.bz2 RT wrote: > Tom Tromey wrote: > >>>>>>> "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. > > I haven't looked at this in detail. I suspect the problem is that > Insight is no longer actively maintained, and so it's difficult to get a > version of insight that uses the current gdb. > > There's no point filing bugs that are Insight-specific; there's no one > to work on them. A trivial licensing problem has lead to gdb having no > usable GUI (that I know of, anyway; and I've used both ddd and insight). > If anyone at the FSF knows of a way to debug multi-threaded > shared-library apps without a GUI, then I'd be really pleased to hear > from them. And, if I don't hear from them, I guess that they'll agree > that gdb is an 80's dinosaur, and it's time to put it to bed. What is the licencing problem? I've been going to make a new gui for gdb, but i'm busy with too much other stuff.