Messages in this thread | | | Date | Sun, 31 Mar 1996 13:14:48 -0800 (PST) | From | root <> | Subject | GDB Stack not complete (1.3.79) |
| |
Hiya,
Sorry if this is the wrong forum (if it is, please direct me to the correct one). Every since I upgraded to 1.3.X I have had problems using core dump files, but yesterday I upgraded to 1.3.79 and gdb now *almost* functions again.
The problem is, that the last stack frame does not appear when loading a core file, let me give an example:
(gdb) bt #0 in __kill() #1 in gsignal() #2 in __ypbindlist() #3 in gsignal() <---- missing frame "in crash_it()" here #4 in interpreter() #8 in run() #9 in main([snip]) #10 in start()
There should have been a frame between #3 and #4 name "crash_it()" which is a procedure calling abort() (no its not optimized or inline). But strangely enough the last procedure where the crash occurs is always non existant. This even happens when gdb'ing the binary file directly.
Anyone know what I can do?
I am using gdb 4.14 (statically linked ELF), gcc 2.7.2p (libc 5.2.10), kernel 1.3.79.
Thanks,
Michael seifert@valhalla-usa.com
| |