Do you get segmentation faults for the application or for gdb? If the former, try the backtrace (bt) command and see where and why it crashes.
Do you get segmentation faults for the application or for gdb? If the former, try the backtrace (bt) command and see where and why it crashes.
The seg fault is coming from my application, not gdb. Here's the stack trace... doesn't seem very helpful though.
#0 0x005c0065 in ?? ()
#1 0x7c90eb94 in ntdll!LdrAccessOutOfProcessResource () from C:\WINDOWS\system32\ntdll.dll
#2 0xeb0075fc in ?? ()
#3 0x00007c90 in ?? ()
#4 0x00630000 in ?? ()
#5 0x006e0049 in ?? ()
#6 0x002e006a in ?? ()
#7 0x00000064 in ?? ()
#8 0x07f40000 in ?? ()
#9 0xfc780000 in ?? ()
#10 0x104b0075 in ?? () from C:\Qt\4.3.4\bin\QtGuid4.dll
#11 0xc0d87c90 in ?? ()
#12 0x31dc0197 in ?? ()
#13 0x32127c91 in ?? ()
#14 0x00087c91 in ?? ()
#15 0x0001c015 in ?? ()
#16 0x83b00000 in ?? ()
#17 0xf9cc0000 in ?? ()
#18 0x00010075 in ?? ()
#19 0xff040000 in ?? ()
#20 0xee180075 in ?? ()
#21 0x63a87c90 in ?? ()
#22 0x00007c91 in ?? ()
#23 0xff140000 in ?? ()
#24 0x62da0075 in ?? ()
#25 0x00007c91 in ?? ()
#26 0x69700000 in ?? ()
#27 0xff600025 in ?? ()
#28 0xff400075 in ?? ()
#29 0xff5c0075 in ?? ()
#30 0x00010075 in ?? ()
#31 0x00000000 in ?? ()
Again, when removing the breakpoints, the program runs fine in gdb. I am stumped![]()
The trace doesn't make sense. I suggest you try some other version of gdb - it may be conflicting with your mingw or something like that.
Bookmarks