Incompatibilities between gcc-4.4.0 and gdb-5.2.1 of the MinGW toolchain
bundled in this version of Python(X,Y) cause Eclipse's debugger to hang
indefinitely when debugging C/C++ programs.
Version: 2.6.5.1
Components Installed: Full (all)
Installation Directories: default path
Target Users: All users
OS: XP
Logged in as: Administrator
Cleaning prior to installation: N/A -- Python(X,Y) was not previously
installed.
To reproduce the problem:
1. Installed Python(X,Y)-2.6.5.1 for all users, and with a full complement
of options.
2. Launch Eclipse
3. Create a Hello World C or C++ project.
4. Attempt to debug the resulting binary executable program.
The expected output:
Proper operation of the debugger.
What I see instead:
The debugger hangs indefinitely.
Additional information -- (two sections: Another Symptom and Possible Fix):
Another Symptom:
The following error message from gdb sheds some light on this issue:
$ gdb hello_world
GNU gdb 5.2.1
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as
"i686-pc-mingw32"...c:/cygmnt/prj/pkg/src/gdb/mingw32/gdb/dwarf2read.c:985:
gdb-internal-error: read_comp
_unit_head: dwarf from non elf file
An internal GDB error was detected. This may make further
debugging unreliable. Quit this debugging session? (y or n) n
Create a core file containing the current state of GDB? (y or n) n
(gdb) quit
Possible Fix:
Replacing the MinGW gdb installation with gdb-6.8-mingw-3.tar.bz2 seems to
correct the issue.
Original issue reported on code.google.com by jvhu...@gmail.com on 1 Jun 2010 at 10:10
Original issue reported on code.google.com by
jvhu...@gmail.com
on 1 Jun 2010 at 10:10