On Mon, May 21, 2012 at 11:40:12AM -0700, Bryce Schober wrote:
> This is happening again, this time on a char[1024]. I note that while it's in
> this mode, the mouse-over also stays on top of other windows. That's helpful,
> to let me know if/when it wakes up, thanks for that feature! ;-) This time it
> only took ~1.5 minutes to expand, not too bad! ;-) The debugger log shows
> nothing particularly suspicious (I note it does even have timestamps to
> validate my assertions). It just shows the expected expansions:
>
> <Rebuild Watchmodel 29>
> sFinished retrieving data
> <264bb options:fancy,autoderef,dyntype,partial vars:local.configfilename
> expanded:local.configfilename,tooltip.636f6e66696766696c656e616d65
> typeformats:
> formats: watchers:
> >&"bb options:fancy,autoderef,dyntype,partial vars:local.configfilename
> expanded:local.configfilename,tooltip.636f6e66696766696c656e616d65
> typeformats:
> formats: watchers:\n"
> >~"data=[{iname=\"local.configfilename\",name=\"configfilename\",addr=\
> "0xbffff094\",numchild=\"1\",childtype=\"char\",childnumchild=\"0\",addrbase=\
> "0xbffff094\",addrstep=\"0x1\",children=[{value=\"47\",},{value=\"104\",},
> {value=\"111\",},{value=\"109\",},{value=\"101\",},{value=\"47\",},{value=\"98\
> ",},{value=\"115\",},{value=\"99\",},{value=\"104\",},
> <snip\>
> ],type=\"char [1024]\",value=\"@0xbffff094\",},,],typeinfo=[]\n"
> >264^done
Both command and output look as expected.
Could you check where the 1.5 minutes are spend, i.e. before the
response shows up in the log (pointing to the gdb side), or
afterwards (pointing to the watch model)?
> Are you interested in the full debugger log?
Yes, please.
> Is there some way I can set the default char-array interpretation to
> not blow up on my like this?
The "per-type" format settings are persistent.
Andre'
_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/qt-creator
