http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47308
Zouzou <internet at 123gen dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |internet at 123gen dot com --- Comment #18 from Zouzou <internet at 123gen dot com> 2012-06-16 12:55:20 UTC --- Hi, Using GCC 4.7 & GDB 7.4 from a regular MinGW install (mingw-get install gcc gdb), I can reproduce this. Just adding -g-dwarf4 is enough to create the problem. It seems GDB 7.4 chokes on the DWARF 4 information. The test case is then very simple: just a int* x = 0; *x = 2; or any other simple crash. When the program crashes, GDB displays that error instead of interrupting the program and doesn't allow getting a backtrace. I would love to see this fixed in order to use DWARF 4 (its duplicated type DIE elimination especially). Here are my GCC & GDB configs; feel free to ask for more information: gcc -v: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=c:/mingw/bin/../libexec/gcc/mingw32/4.7.0/lto-wrapper.exe Target: mingw32 Configured with: ../gcc-4.7.0/configure --enable-languages=c,c++,ada,fortran,objc,obj-c++ --disable-sjlj-exceptions --with-dwarf2 --enable-shared --enable-libgomp --disable-win32-registry --enable-libstdcxx-debug --disable-build-poststage1-with-cxx --enable-version-specific-runtime-libs --build=mingw32 --prefix=/mingw Thread model: win32 gcc version 4.7.0 (GCC) gdb -v: GNU gdb (GDB) 7.4 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i686-pc-mingw32". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>.