Re: gftp backtrace

[Richard Hult <rhult hem2 passagen se>]

On 13 Mar, hitch wrote:
> 
> I'm sure that there are quite a few of us on the list that don't know
> how to do a backtrace (including me) and it would save a lot of time and
> "oh my GOSH!  YOU DON"T KNOW HOW TO DO A BACKTRACE??  EVERYONE SHOULD BE
> ABLE TO BACKTRACE!!" comments if y'all posted it on the general list....

There are two ways. Either you start the program with the debugger:

gdb <program_name>

then type at the gdb prompt:

(gdb) run

then when the program crash, type

(gdb) bt

and then you get your backtrace. If someone asks you to print the value
of a specific variable, just type:

(gdb) p <variable>

when you're done, type

(gdb) quit


The other way is used if you have a core-dump you want to examine. First
you can see which program that dumped it, by typing at the shell prompt:

# file core

which then tells you which file it came from. Then start gdb with that
program (including the path) and the core:

# gdb </path/to/file/filename> core

and then type 'run' and follow the instructions above.

Hope it helps
Richard