gdb output

[Sheldon]

Hi,

I have program that I am trying to debug.
When I use gdb I get the following:

(gdb) backtrace
#0 0x40297664 in ?? ()
#1 0x403671c0 in ?? ()

I have little experience with gdb and debugging C. Does anyone know
what has happened here?

Any help is appreciated,
Sheldon

 

[Barry]

Hi,

I have program that I am trying to debug.
When I use gdb I get the following:

(gdb) backtrace
#0 0x40297664 in ?? ()
#1 0x403671c0 in ?? ()

I have little experience with gdb and debugging C. Does anyone know
what has happened here?

Any help is appreciated,
Sheldon

A user typed in "backtrace" and gdb displayed the stack frames.

 

[Sheldon]

Barry skrev:

A user typed in "backtrace" and gdb displayed the stack frames.

Yes but do you know what these frames mean?

/S

 

[Jens Thoms Toerring]

Barry skrev:
Yes but do you know what these frames mean?

This is off-topic here since it's not about the C language but
about some tool you're using - you probably better ask in e.g.
gnu.gcc.help after you have read the gdb documentation... So
only a short answer: try compiling with the '-g' option (to
retain debugging info in the final program) and look again
what 'backtrace' then shows you. I guess this will answer your
question;-)
Regards, Jens

 

[Ico]

I have program that I am trying to debug.
When I use gdb I get the following:

(gdb) backtrace
#0 0x40297664 in ?? ()
#1 0x403671c0 in ?? ()

I have little experience with gdb and debugging C. Does anyone know
what has happened here?

No way to tell - compile with debugging enabled (-g) and try again

 

[Sheldon]

Ico skrev:

No way to tell - compile with debugging enabled (-g) and try again

I understand. The thing is that I am using (-g) and this is what
baffles me: I acnnot tell what is wrong, even after I read the manual
and some examples from online manuals.
I will check with the gcc site.
Thanks!

/S

 

[Ico]

Ico skrev:


I understand. The thing is that I am using (-g) and this is what
baffles me: I acnnot tell what is wrong, even after I read the manual
and some examples from online manuals.

Did you also use -g at the linking stage ?

 

[Sheldon]

Ico skrev:

Did you also use -g at the linking stage ?

Yes I did.

/S

 

[Richard Tobin]

When I use gdb I get the following:

(gdb) backtrace
#0 0x40297664 in ?? ()
#1 0x403671c0 in ?? ()

Quite likely the bug in your program overwrote the stack, so the
debugger is confused. You could try setting breakpoints to narrow
down where the failure happened.

-- Richard