...another one:
After the merge attaching to a process makes GDB crash. This used to work in the branch...?! Here is the debug log:
[debug]Command-line: C:\Devel\GCC46TDM\bin\gdb.exe -nx -fullname -quiet
[debug]Working dir : D:\Code\Dummy
Starting debugger: C:\Devel\GCC46TDM\bin\gdb.exe -nx -fullname -quiet
done
[debug]> set prompt >>>>>>cb_gdb:
Registered new type: wxString
Registered new type: STL String
Registered new type: STL Vector
Setting breakpoints
Attaching to program with pid: 2928
[debug](gdb) >>>>>>cb_gdb:
[debug]> show version
[debug]GNU gdb (GDB) 7.3
[debug]Copyright (C) 2011 Free Software Foundation, Inc.
[debug]License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
[debug]This is free software: you are free to change and redistribute it.
[debug]There is NO WARRANTY, to the extent permitted by law. Type "show copying"
[debug]and "show warranty" for details.
[debug]This GDB was configured as "mingw32".
[debug]For bug reporting instructions, please see:
[debug]<http://www.gnu.org/software/gdb/bugs/>.
[debug]>>>>>>cb_gdb:
[debug]> set confirm off
Debugger name and version: GNU gdb (GDB) 7.3
[debug]>>>>>>cb_gdb:
[debug]> set width 0
[debug]>>>>>>cb_gdb:
[debug]> set height 0
[debug]>>>>>>cb_gdb:
[debug]> set breakpoint pending on
[debug]>>>>>>cb_gdb:
[debug]> set print asm-demangle on
[debug]>>>>>>cb_gdb:
[debug]> set unwindonsignal on
[debug]>>>>>>cb_gdb:
[debug]> set print elements 0
[debug]>>>>>>cb_gdb:
[debug]> set debugevents on
[debug]>>>>>>cb_gdb:
[debug]> set disassembly-flavor att
[debug]>>>>>>cb_gdb:
[debug]> catch throw
[debug]No symbol table is loaded. Use the "file" command.
[debug]Catchpoint 1 (throw)
[debug]>>>>>>cb_gdb:
[debug]> source C:\Devel\CodeBlocks\share\codeblocks/scripts/stl-views-1.0.3.gdb
[debug]>>>>>>cb_gdb:
[debug]> attach 2928
[debug]gdb: windows_init_thread_list
Child process PID: 2928
[debug][New Thread 2928.0xb74]
[debug][New Thread 2928.0xd98]
[debug][New Thread 2928.0xe2c]
[debug][New Thread 2928.0x35c]
[debug][New Thread 2928.0x104c]
[debug]=b74 code=LOAD_DLL_DEBUG_EVENT)
-> CRASH.
I'll try on the command lien to see what happens there... However, can somebody try to attach to a process, too?
EDIT: Crashes on the command line, too... WTF?!