[Bug c++/23639] QtCreator stall and timeout after 40 seconds due to GDB

mgarvin at panix dot com sourceware-bugzilla@sourceware.org
Thu Sep 13 01:52:00 GMT 2018


https://sourceware.org/bugzilla/show_bug.cgi?id=23639

--- Comment #4 from Mark Garvin <mgarvin at panix dot com> ---
Simon,  I did locate Qt's log file that has some info about interaction with
GDB.  This seems to be the relevant line at the point where it stalls:

--------------------------------------------------------------------------

d252: python
theDumper.fetchVariables({"autoderef":1,"context":"","displaystringlimit":"100","dyntype":1,"expanded":["return","inspect","local","watch"],"fancy":1,"formats":{},"nativemixed":0,"partialvar":"","passexceptions":0,"qobjectnames":1,"resultvarname":"","stringcutoff":"10000","token":252,"typeformats":{},"watchers":[]})
d253: -exec-continue
dTIMED OUT WAITING FOR GDB REPLY. COMMANDS STILL IN PROGRESS: "-exec-continue",
"python
theDumper.fetchVariables({"autoderef":1,"context":"","displaystringlimit":"100","dyntype":1,"expanded":["return","inspect","local","watch"],"fancy":1,"formats":{},"nativemixed":0,"partialvar":"","passexceptions":0,"qobjectnames":1,"resultvarname":"","stringcutoff":"10000","token":252,"typeformats":{},"watchers":[]})"

----------------------------------------------------------------------------

Not sure why I'm seeing "python theDumper" in a log for a C++ debug session. 
Does that make sense?  Perhaps GDB uses a python script somewhere in the
process.

I don't see anything that I recognize in "COMMANDS STILL IN PROGRESS: " so
these are probably names for internal variables and processes.

I can send more of the log file, but this seems like a good start.  Please let
me know if you can think of any tests that can be done to correlate this with
QtCreator's debugger, or with C++ source code.

I still find it odd that setting a breakpoint anywhere in a certain range of
C++ source will cause the bug to occur.  So setting it on any line from 100 to
150 will cause the stall, but setting it on line 99, or on line 151 will behave
normally.

It's especially unsettling in that I need to guarantee the integrity of the 
code that I'm writing, and this cannot be localized to any single C++ source
statement or function.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the Gdb-prs mailing list