How to get a useful backtrace in Cygwin?

▲
3
▼

Although I have compiled my C program with -g -O0, the backtrace I get from gdb is useless:

(gdb) bt
#0  0x6113759d in wordfree () from /cygdrive/c/cygwin/bin/cygwin1.dll
#1  0x75141375 in OutputDebugStringA () from /cygdrive/c/Windows/system32/KERNELBASE.dll
#2  0x40010006 in ?? ()
#3  0x00000000 in ?? ()

Is there any way to get a useful backtrace in Cygwin?

My gdb version is 7.3.50.20111026-cvs (cygwin-special), gcc is 4.5.3.

c
debugging
gdb
cygwin
backtrace
asked on Stack Overflow May 24, 2012 by Erik

2 Answers

▲
0
▼

"bt full" should give you better results.

answered on Stack Overflow May 24, 2012 by qwertyboy
▲
0
▼

Make sure you have the correct thread selected. try info threads and then thread <num>.

answered on Stack Overflow Nov 6, 2012 by Scott

User contributions licensed under CC BY-SA 3.0