traceback troubles
Robert Schweikert
rjschwei@mindspring.com
Sat Dec 9 03:54:00 GMT 2000
Is there a way to figure out where things went wrong with this type of
traceback?
Program terminated with signal 11, Segmentation fault.
#0 0x400035a6 in ?? ()
(gdb) where
#0 0x400035a6 in ?? ()
#1 0x4000bffc in ?? ()
#2 0x40001f69 in ?? ()
#3 0x40001eda in ?? ()
This is version 4.18 of gdb.
The code was compiled with gcc 2.95.2 on RedHat 6.1 without the -g
option. However, shouldn't I still get a stacktrace that at least points
me to the routine where things went wrong. This is C++ code.
Any help is appreciated.
Thanks,
Robert
--
Robert Schweikert MAY THE SOURCE BE WITH YOU
rjschwei@mindspring.com LINUX
More information about the Gdb
mailing list