Help with backtrace

[GoinEasy9]

I've been asked to send a backtrace to a bugzilla I filed for nautilus locking up when I try to use it to get to /usr/share/man/man1. The icons for man appear but then one core of the cpu is at 100% and when I try to "x" out it says "man is not responding" and I have to force quit.

I found gdb in the docs, but, since it's my first time trying this, I'm doing something wrong.
I've used debuginfo-install nautilus to get the debuginfos, so I have all the files I need, I just need an example of how the gdb line should appear in the terminal.
gdb stack backtrace? And where do I put the option to what file I want it to print to.

Thanks for any help.

OR, did I pick the wrong app for a backtrace, and, is there a simplier way?

---------- Post added at 05:52 PM CDT ---------- Previous post was at 03:28 PM CDT ----------

Or can someone point me to a doc with the preferred fedora way of submitting a backtrace? I confess, this is all totally new to me. In all my years in Linux, I've never had to do this manually before.

---------- Post added at 06:44 PM CDT ---------- Previous post was at 05:52 PM CDT ----------

Never mind, I finally found the info in the wiki:
http://fedoraproject.org/wiki/StackTraces#How_do_I_generate_a_backtrace.3F

---------- Post added at 07:45 PM CDT ---------- Previous post was at 06:44 PM CDT ----------

Even with step by step instructions I can't get a backtrace, so I'm guessing I had the commands right, but something else is going on.
gdb exits before I can run nautilus till it freezes even with all the correct debuginfos.

[karo1170]

[QUOTE=GoinEasy9;1394755]I've been asked to send a backtrace to a bugzilla I filed for nautilus locking up when I try to use it to get to /usr/share/man/man1. The icons for man appear but then one core of the cpu is at 100% and when I try to "x" out it says "man is not responding" and I have to force quit.

I found gdb in the docs, but, since it's my first time trying this, I'm doing something wrong.
I've used debuginfo-install nautilus to get the debuginfos, so I have all the files I need, I just need an example of how the gdb line should appear in the terminal.
gdb stack backtrace? And where do I put the option to what file I want it to print to.

Thanks for any help.

OR, did I pick the wrong app for a backtrace, and, is there a simplier way?[COLOR="Silver"]

Do you have abrt installed? This might catch the crash and supply you with a backtrace.

Otherwise, you can try the following procedure with gdb:

1. Run <program>
2. Open terminal and run:
> gdb /usr/bin/<program> `pidof <program>`
3. In GDB console type "continue"
4. Reproduce crash
5. Get backtrace in GDB console by typing "bt"

Not sure, if this works, but might be worth trying.

Regards
karo

[GoinEasy9]

Thanks karo1170
abrt did not pick up the crash, it was always easy when abrt was working.
gdb is what I found, that and strace, but gdb would be the one that let the program run till it crashed.
One of the options "continue" I didn't try, used run to start nautilus, but then nautilus threw off errors and exited. Maybe "continue" will help after that, I'll try when I get back home.

Thanks Again.