Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!sdd.hp.com!news.cs.indiana.edu!ux1.cso.uiuc.edu!timothyg From: timothyg@ncsa.uiuc.edu (Timothy Gallivan) Newsgroups: comp.sys.atari.st.tech Subject: Re: Re: using GDB Message-ID: <1991May23.162701.11211@ux1.cso.uiuc.edu> Date: 23 May 91 16:27:01 GMT References: <91142.182214ZVD007@DMSWWU1C.BITNET> Sender: usenet@ux1.cso.uiuc.edu (News) Organization: Nat'l Ctr for Supercomp App (NCSA) @ University of Illinois Lines: 34 Originator: timothyg@harriett In article <91142.182214ZVD007@DMSWWU1C.BITNET>, Ulrich Kuehn writes: |> First of all I want to thank all who replied. |> |> I was told that I have to use the -gg option to get debugging info and then |> have to use sym-ld. |> But there is a big problem: when I enter gdb and try to read in the sym-file |> I get two bombs; searching for a solution, I found, that gdb supports no |> longer the -gg option, one has to use the -g option. So, I tried that, and |> gdb doesnt crash, it can set breakpoints and list the source, but when I |> run the program, it allways receives a signal null and when I try to cont |> the I get two bombs, but the debugger doesnt crash, the program is just halted. |> Is there anyone with a solution of this problem? |> |> Thanks in advance |> U.Kuehn I second this plea for help (actually my fourth). Regarding the -gg option, I received the following from Jwahar Bammi: >compile your program with -gg -D__NO_INLINE__ and it should hopefully work >gdb is very much out of date. gnu has dropped support for -gg format, >and the latest versions of the assembler dont support the additional >info produced by -gg. one day i'll get around to doing gdb properly. Defining __NO_INLINE__ gets rid of the two bombs, but I also get the null signal. You are supposed to be able to tell gdb to ignore the null signal, but when I try to do this, gdb tells me that 0 (the null is signal number 0) is not a valid signal number. So, I can't change anything. I have about given up on gdb, and have reverted to using Gdb (the Gallivan debugger--lots of print statements!). Tim Gallivan timothyg@ncsa.uiuc.edu