Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!ux1.cso.uiuc.edu!timothyg
From: timothyg@ncsa.uiuc.edu (Timothy Gallivan)
Newsgroups: comp.sys.atari.st.tech
Subject: Re: GDB question
Message-ID: <1991May1.150644.11919@ux1.cso.uiuc.edu>
Date: 1 May 91 15:06:44 GMT
References: <91119.163834ZVD007@DMSWWU1C.BITNET> <1080@uqcspe.cs.uq.oz.au>
Sender: usenet@ux1.cso.uiuc.edu (News)
Organization: Nat'l Ctr for Supercomp App (NCSA) @ University of Illinois
Lines: 28
Originator: timothyg@harriett


	[in response to a question about how to use the gnu debugger]

|>      $ gcc -c -gg foo.c    # compile `foo.c'
|>      $ gcc -o foo.prg foo.o # linkwith normal `gcc-ld.ttp'
|>      $ sym-ld  -r -o foo.sym $(GNULIB)"crt0.o foo.o -lgnugdb  (or -lgdb)
|>                            # link with `sym-ld.ttp' to get symbol file
|>      $ gdb
|>      * exec-file foo.prg   # executable (`gcc-ld.ttp' linked Atari
|>                              executable)
|>      * symbol-file foo.sym  # symbols file (`sym-ld.ttp' `-r -o' linked)
|>      * run
|>      * <start doing gdb commands here>
|>       : : :
|>      * q
|>      $                     # back
|>

Well, that is what the instructions say. When I follow this procedure,
I get bombs after 'symbol-file foo.sym'. I have yet to hear from anyone
who has been able to get gdb to work. I have heard from several people
who cannot. Good Luck!

Can anyone help the poor souls who are without a debugger?
  

Tim Gallivan
timothyg@ncsa.uiuc.edu