traceback troubles

[Fernando Nasser]

Robert Schweikert wrote:
> 
> 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.
> 

Robert,

The debug information contains, among many other things, where the
functions start.  If you have no debug information passed to the debugger
it cannot guess where these addresses belong.

Bottom line: if you want symbolic debugging, use "-g".


-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9