[ILUG] GDB Pointers? Fedora 13 x86_64 (long Post)

[Josh Glover]

Damn, Paul! I just suggested gdb because Frank mentioned it; were it
myself in need of a backtrace, I'd simply send SIGSEGV to the
offending process group and rip into the resulting core files with a
binary editor (hex is for sissies). That I wrote myself. In IA64
machine code. With unrolled loops. Using an Atari paddle controller as
a binary input device. Running at 400 baud on a serial port driver
that I wrote myself. Loaded at runtime into a kernel that I wrote
myself. In IA64 machine code...

I said good day sir!

On 2010-03-04, paul at clubi.ie <paul at clubi.ie> wrote:
> On Wed, 3 Mar 2010, Rory Browne wrote:
>
>> Personally for a freeze, first thing I'd check is the general process
>> statisitcs ( CPU, Memory, etc ), using top.
>
> I'd start with gdb actually. It will tell you exactly where the thing
> is spinning around.
>
> $ gdb app [optional core or pid to investigate]
> (gdb) run
> <do whatever you need to do to wedge your process>
> <press ctrl+c - gdb will catch this>
> (gdb) bt
> <see what your programme is up to>
> (gdb) cont
> <press ctrl+c again>
> (gdb) bt
> ...
> (gdb) cont
>
> etc..
>
> Course, anyone who uses the "bt" command is a big pansy. Real hackers
> use print/x and mentally unwind the stack in their heads, only
> ocassionally cross-checking addresses with disassemble...
>
> (That may sound like I'm joking, but the mdb debugger popular with
> Solaris kernel devs doesn't have a symbolic stack unwinding command
> :) )
>
> regards,
> --
> Paul Jakma	paul at jakma.org	Key ID: 64A2FF6A
> Fortune:
> Bachelor:
>  	A man who chases women and never Mrs. one.
> --
> Irish Linux Users' Group mailing list
> About this list : http://mail.linux.ie/mailman/listinfo/ilug
> Who we are : http://www.linux.ie/
> Where we are : http://www.linux.ie/map/
>

-- 
Sent from my mobile device

Cheers,
Josh