home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.next.programmer:5906 comp.lang.c++:13136
- Newsgroups: comp.sys.next.programmer,comp.lang.c++
- Path: sparky!uunet!elroy.jpl.nasa.gov!usc!sol.ctr.columbia.edu!ira.uka.de!math.fu-berlin.de!news.th-darmstadt.de!aida!uli
- From: uli@aida.intellektik.informatik.th-darmstadt.de (Ulrich Grepel)
- Subject: Re: Replacing NeXT cc with gcc-2.2.2
- Message-ID: <1992Sep01.112153.31711@news.th-darmstadt.de>
- Sender: uli@aida (Ulrich Grepel)
- Date: Tue, 01 Sep 1992 11:21:53 GMT
- References: <1992Aug31.164909.7198@fcom.cc.utah.edu>
- Nntp-Posting-Host: aida.intellektik.informatik.th-darmstadt.de
- Organization: TH Darmstadt
- Lines: 16
-
- In article <1992Aug31.164909.7198@fcom.cc.utah.edu>, swillden@news.ccutah.edu (Shawn Willden) writes:
- |>
- |> 5) Is 2.2.2 compatible with the NeXT gdb or would I have to get gdb-4.6 as
- |> well?
- |>
- Unfortunately, as previously posted, NeXTs gdb 3.x doesn't run perfectly
- with gcc 2.2.2 output. But you can make more than backtraces if you
- use the gcc option -gstabs to generate the debugging info. This is
- understood by gcc 3.x. Unfortunately again, the stabs format doesn't
- have all the abilities of gcc 3.x (or even 4.x).
-
- Has anyone succeeded in getting gdb 4.6 adapted to NeXT? What gdb version
- is used in NS 3.0? (Anyone should be allowed to answer that, now there are
- some NS 3.0 final releases out!)
-
- Uli
-