From: corywest@rice.edu (Cory West) Subject: GDB is possessed -- Any ideas? Date: 14 Aug 1992 00:12:41 GMT
Hello all. I have been having some problems with gdb and was
hoping that y'all could help out. I've already sent this to the GCC
mailing list, but haven't heard a peep yet, so I thought I'd throw
it out a little further. First, here's my version information:
Linux Version 0.97 PL1 (On a 486-33/4)
GDB 4.6 (Compiled with GCC 2.2.2d and linked static)
GCC 2.2.2 and GCC 2.2.2d
Now, here's the problem: I compiled gdb first with gcc -V
2.2.2 under linux v 0.96c PL2, but this died at the final link with a
_setjmp problem. This was no new problem and so I compiled in with
regular gcc 2.2.2d. I tried to link it dynamically both with and without
jump tables, but again it always died with a memory corruption error and
so I linked it statically and went on my merry way.
So far so good, I had a working gdb (statically linked) that
would happily let me debug programs and the like.
Then I upgraded to Linux v 0.97 PL1 and re-installed my gcc
2.2.2d (as per HJ's instructions). I recompiled gdb with gcc 2.2.2d
and linked it statically, but it no longer works. I compiled
several test case programs with the new gcc 2.2.2d and the -g option
and ran them through gdb, but when I try to set breakpoints, I always
get the error "No line xxx in file "file.c"." If I run and interrupt a
program and try to step through it, I get:
Current function has no line number information. No data
available on pc function.
It's as if gcc libg.a was broken or something, but I don't know for
sure.
Has anyone had these problems or can anyone point me in a
new direction? I am running out of things to try. If you need
more information, just let me know. Thanks a bunch in advance!
Cory West
corywest@rice.edu