Driving gdb

[Hal Murray]

devel at ntpsec.org :
> Thread 4 "ntpd" received signal SIGSEGV, Segmentation fault. [Switching to
> Thread 0x75b1a460 (LWP 26062)] 0x76cfb6fc in strlcpy () from /usr/lib/
> libbsd.so.0

> Any idea how to make gdb more useful here? 

"bt" (for backtrace) gives you the stack trace
In many cases, that's enough.

"up" switches gdb to looking at the calling stack frame
"print xxx" prints variables or expressions


-- 
These are my opinions.  I hate spam.