[Qt-creator] Debugger-resistant routine

[Andre Poenitz]

On Sun, Aug 22, 2010 at 06:14:36PM +0000, Bob Babcock wrote:
> Andre Poenitz <andre.poenitz at mathematik.tu-chemnitz.de> wrote in
> news:i4racs$26e$1 at eple.troll.no: 
> 
> > Ok. My crystal ball now says there is a 'char' or 'char *' in B that's
> > either not initialized yet or contains/points to data outside the 7
> > bit range. Is that right?
> 
> Your crystal ball is correct.  The empty watch pane seems to be triggered 
> by:
>   unsigned char tempc;
> Initializing tempc to a 7-bit value fixes it; initializing to a value with 
> the high-bit set breaks it.  It doesn't matter whether the unsigned keyword 
> is present or not.
> 
> Thanks for figuring this out. 

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

> Debugging with a broken debugger is not fun.

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.

Andre'