[Qt-creator] Debugger-resistant routine

[Andre Poenitz]

On Sat, Aug 21, 2010 at 07:28:25PM +0000, Bob Babcock wrote:
> Bob Babcock <wssddc at nospam.gis.net> wrote in
> news:Xns9DDBD2118CBDwssddcgisnet at 62.70.27.71: 
> 
> > Environment:
> >   Windows XP
> >   Qt 4.7 beta 2
> >   Qt Creator 2.0.80 or snapshot from 21-Aug-2010 00:32
> >   MinGW and GDB
> > 
> > Problem:
> > A calls B calls C.  When stepping through B with the debugger in
> > Creator, the Locals and Watchers window is empty, insert new watch
> > item does nothing, and hovering the mouse over variables does not show
> > values in a tooltip.  All of these functions work when stepping
> > through A or C, but it's B I need to debug.  I don't think B is
> > clobbering anything, if only because I insert a breakpoint before it
> > does anything. 
> 
> In the debugger view, I see:
> 
> DUMPER FAILED: 57^error,data={msg="Error occurred in Python command.",
> logstreamoutput="bb options:fancy vars: expanded: typeformats: 
> formats: watchers:4469736b6e6f23746f6f6c7469702e78\n
> Error occurred in Python command.\n",consolestreamoutput=
> "Traceback (most recent call last):\n
> File \"D:/Comp/Qt/qtcreator-2.0.80/share/qtcreator/gdbmacros/dumper.py\", 
> line 1046, in invoke\n    print('data=[' + d.output + ']')\n
> File \"<string>\", line 11, in write\n
> UnicodeEncodeError: 'ascii' codec can't encode character u'\\xf0'
> in position 4062: ordinal not in range(128)\n"}

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?

Andre'