Details
-
Bug
-
Resolution: Moved
-
Not Evaluated
-
None
-
Qt Creator 2.2.0
-
None
-
Windows
Description
The gdb process errors out with the following log:
dALL COMMANDS DONE; INVOKING CALLBACK
<46maint print msymbols C:/Users/JoLi/AppData/Local/Temp/gdb_ns_.mz3772
>&"maint print msymbols C:/Users/JoLi/AppData/Local/Temp/gdb_ns_.mz3772\n"
>46^done
dFOUND NON-NAMESPACED QT
<47-break-insert -f 'qFatal'
>&"warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)\n"
(Internal error: pc 0x0 in read in psymtab, but not in symtab.)
>&"\n"
>&"warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)\n"
(Internal error: pc 0x0 in read in psymtab, but not in symtab.)
>&"\n"
>&"warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)\n"
(Internal error: pc 0x0 in read in psymtab, but not in symtab.)
>&"\n"
>&"warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)\n"
(Internal error: pc 0x0 in read in psymtab, but not in symtab.)
>&"\n"
dHANDLE GDB ERROR: The gdb process crashed some time after starting successfully.
dGDB PROCESS FINISHED, status 1, code -1073741819
dNOTE: ENGINE ILL ******
Workaround is to create an easy-to-find-for-gdb qFatal() in your main file. This will cause gcc to emit a warning though, and you'll need to provide a reasonable implementation of it.
void qFatal(const char *...)
{
return;
}
Attachments
Issue Links
- relates to
-
QTCREATORBUG-5200 Fix "Internal error: pc 0x0 in read in psymtab, but not in symtab."
- Closed
-
QTCREATORBUG-5184 QtCreator debug helpers fail and show "d" as children of objects
- Closed