[Mingw-users] "Internal error" in gdb 7.0.50.20100202

[Hans-Jochen T. <hj...@tx...>]

The short of it is:

Trying to debug an app with gdb 7.0.50.20100202 produces an error

   ../../gdb-7.0.50.20100202/gdb/breakpoint.c:6481: internal-error: expand_line_sal_maybe: Assertion `found' failed.
   A problem internal to GDB has been detected,
   further debugging may prove unreliable.

before the first breakpointable instruction in my source code is reached (a wxWidgets 2.8.10 based app).  This gdb version will operate the "minimal" sample of wxWidgets without problems.

gdb 6.8 fails with an error

   No line 0 in file "../jetlabwx.cpp".

also before the first breakpointable instruction (which is in jetlabwx.cpp) when trying to debug the same executable.

I appreciate any hints and suggestions as to what to do.  The long of it follows below.

Cheers,          Jochen



The long of it is (sorry, it's long):

Platform:

HP xw4300 workstation
1 GB RAM
Windows XP SP3

MinGW 5.1.6 automatic installed (downloaded 20100209,06:59 GMT)
gcc 3.4.5
gdb 7.0.50.20100202 or gdb 6.8 (downloaded 20100305, afternoon CST)

Eclipse Galileo for C/C++:
   Platform              3.5.2.M20100210-0800
   EPP CPP Feature       1.2.2.20100209-1511
   CDT                   6.0.2.2010002050614

Application "jetlab4": Main executable has ca. 160 source files,
11 MB executable including debugging info (-g3) and no optimization (-O0).
wxWidgets 2.8.10


Problem:

I am porting the app from BCB5p1 to gcc.  The program compiles, links and starts running though part of its initialization sequence, including a selection dialog offered to the user, then crashes.  Therefore I picked up gdb to do some debugging.

gdb fails starting the app with a hint on a supposed internal error (7.0...) or some sort of failure finding/reading the lead source file (6.8).  7.0 succeeds with the "minimal" sample of wxWidgets, and my colleague has another wxWidgets based app, not quite as large app as mine, running fine under gdb 7.0.50.10200202 as well.  gdb 6.8 gets confused with the problem app when trying to run the "minimal" sample.

The symptoms are:

Error window pops up (both gdb versions):
-----------------------------------------begin
   Problem occurred

   'Launching jetlab4.exe' has encountered a problem.
   Error stopping at main

   Details:
   Error stopping at main.
     Target request failed: Target is not responding (timed out).
-----------------------------------------end


Console log reports (gdb 7.0.50.20100202):
-----------------------------------------begin
   .gdbinit: No such file or directory.
   Reading symbols from C:JochenProgrammingEclipseSpacejetlab4Debugjetlab4.exe...done.

   ../../gdb-7.0.50.20100202/gdb/breakpoint.c:6481: internal-error: expand_line_sal_maybe: Assertion `found' failed.
   A problem internal to GDB has been detected,
   further debugging may prove unreliable.
-----------------------------------------end


Console log reports (gdb 6.8):
-----------------------------------------begin
   .gdbinit: No such file or directory.

   No line 0 in file "../jetlabwx.cpp".
-----------------------------------------end



Console log reports (gdb 6.8) for minimal.exe
-----------------------------------------begin
   .gdbinit: No such file or directory.

   No source file named jetlabwx.cpp in loaded symbols.
   [New thread 2436.0x28c]
   No source file named jetlabwx.cpp in loaded symbols.
-----------------------------------------end

Note that the minimal program has only a single C++ source
file, minimal.cpp.  jetlabwx.cpp is the "main" file for jetlab4 (above).