From owner-freebsd-current Tue Aug 31 23:55:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 41F6414C2D for ; Tue, 31 Aug 1999 23:55:12 -0700 (PDT) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id XAA19922; Tue, 31 Aug 1999 23:54:04 -0700 (PDT) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Tue, 31 Aug 1999 23:54:04 -0700 Date: Tue, 31 Aug 1999 23:54:04 -0700 (PDT) From: Kip Macy X-Sender: kip@luna To: Alex Zepeda Cc: Richard Cownie , current Subject: Re: gdb-4.17 in FreeBSD 4.0-CURRENT In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: jazepeda@pacbell.net,tich@ma.ikos.com,current@FreeBSD.ORG X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG on 3.2-R gdb-4.18 will core dump without fail when I try to read a core file generated by the C++ program I am developing - gdb-4.17 does not have this problem. -Kip On Tue, 31 Aug 1999, Alex Zepeda wrote: > On Sun, 22 Aug 1999, Richard Cownie wrote: > > > On Sat, 21 Aug 1999, David O'Brien wrote: > > > Are you saying 4.17 is better than 4.18 for debugging C++? Or are you > > > saying you didn't know FreeBSD comes with gdb: > > > > gdb-4.18 is badly broken on all platforms (at least for C++). You can't > > call methods from the gdb command line, and also it frequently freezes > > to the point where you have to kill the window. gdb-4.17 is much better > > for C++. > > Really? I don't use gdb much so, I wouldn't know, but I've seen reports > that KOffice is undebugable with 4.17 (gdb segfaults), but is with 4.18. > Hmm. > > - alex > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message