[Qt-creator] Debugger-resistant routine

[Bob Babcock]

Andre Poenitz <andre.poenitz at mathematik.tu-chemnitz.de> wrote in
news:i4rste$llf$1 at eple.troll.no: 

> Next time please attach the full debugger log nevertheless. That
> crystal ball is rather fragile and often in maintenance...

When I first hit this problem, I didn't even know that there were python 
scripts interpreting gdb output and I had never enabled the debugger log 
window.

> You could temporarily rename share/qtcreator/gdbmacros/dumper.py into
> anything else. That should render the pyhton based dumpers unusable
> and trigger the fallback to the C++ version that should not have the
> problem. 

Yes, that works.  (Just had to do this stepping through another routine 
that has real 8-bit character data.)

I will try to make a simple test case and file a bug report.