[Qt-creator] QtCreator debug shows anonymous union for QVector, QSet, QList, etc

[Alex Reche]

Ok I found something new. In gdb in the command line I did:

(gdb) call (void *)dlopen("/Applications/Qt
Creator.app/Contents/qtc-debugging-helper/92501879/libgdbmacros.dylib",2)
$7 = (void *) 0x0
(gdb) call (const char*)dlerror()
$8 = 0x1c01a55 "dlopen(/Applications/Qt
Creator.app/Contents/qtc-debugging-helper/92501879/libgdbmacros.dylib, 2):
no suitable image found.  Did find:\n\t/Applications/Qt
Creator.app/Contents/qtc-debugging-helper/92501879/libgdbmacros.dylib:
mach-o, but wrong architecture"

So QtCreator is building the wrong architecture for the helpers. How I can
change that?
Can we build the helpers by hand?

    Alex

On Wed, Mar 23, 2011 at 3:41 PM, Alex Reche <al.exreche at gmail.com> wrote:

> No, no more upgrades..
>
> I just noticed that QtCreator, kind of, holds waiting for those commands to
> answer.
> If I stop the debugger, here is the output in the debugger log:
>
> State changed from InferiorStopOk(13) to InferiorShutdownRequested(15).
>
> QUEUE: SHUTDOWN INFERIOR
>
> CALL: SHUTDOWN INFERIOR
>
> 179kill
>
> &"kill\n"
>
> 179^done
>
> INFERIOR SUCCESSFULLY SHUT DOWN
>
> State changed from InferiorShutdownRequested(15) to InferiorShutdownOk(16).
>
> State changed from InferiorShutdownOk(16) to EngineShutdownRequested(18).
>
> QUEUE: SHUTDOWN ENGINE
>
> CALL: SHUTDOWN ENGINE
>
> PLAIN ADAPTER SHUTDOWN 18
>
> INITIATE GDBENGINE SHUTDOWN IN STATE 0, PROC: 2
>
> 180-gdb-exit
>
> 180^exit
>
> GDB CLAIMS EXIT; WAITING
>
> GDB PROCESS FINISHED, status 0, code 0
>
> NOTE: ENGINE SHUTDOWN OK
>
> State changed from EngineShutdownRequested(18) to EngineShutdownOk(19).
>
> State changed from EngineShutdownOk(19) to DebuggerFinished(21).
>
> QUEUE: FINISH DEBUGGER
>
> NOTE: FINISH DEBUGGER
>
> HANDLE RUNCONTROL FINISHED
>
>
> Until here, nothing strange, gdb is properly stoped, and is no longer
> listed in the running processes.
>
> But about 20 seconds later, I have a window saying that gdb is not aswering
> to a command and gives me the choice to wait or kill gdb. If I choice to
> kill it, here is what the debugger log shows:
>
>
>  149: call (void*)qDumpObjectData440(1,0,0,0,0,0,0,0) => <unnamed
> callback>
>
> 150: p (char*)&qDumpOutBuffer => handleQueryDebuggingHelperClassic
>
> TIMED OUT WAITING FOR GDB REPLY. COMMANDS STILL IN PROGRESS:
>
> KILLING DEBUGGER AS REQUESTED BY USER
>
> I hope that gives more information.
>
> BTW, did you see my previous mail? Did I properly simulate QtCretor
> behaviour in the command line gdb? If so, I'll keep looking that way to find
> out why the symbols are not loaded.
>
>      Alex
>
>
> On Wed, Mar 23, 2011 at 3:28 PM, André Pönitz <andre.poenitz at nokia.com>wrote:
>
>> On Wednesday 23 March 2011 15:09:52 ext Alex Reche wrote:
>> > Nothing happens. I also try "p b" where b is a QVector to see if I was
>> doing it right.
>> > Here is the output:
>> >
>> > &"p (char*)&qDumpOutBuffer\n"
>> > &"p qDumpOutBuffer\n"
>> > &"p b\n"
>> > ~"$2 = {\n"
>> > ~" {\n"
>> > ~" d = 0x1d03900, \n"
>> > ~" p = 0x1d03900\n"
>> > ~" }"
>> > ~"\n"
>> > ~"}"
>> > ~"\n"
>> > ^done
>>
>> I am afraid this looks like you are "sorely out of luck" for now.
>>
>> The qDumpOutBuffer contains all the "interesting" data created by the
>> dumpers, if it can't be accessed the dumpers are practically useless.
>>
>> > > Recently I've installed QtCreator 2.1, Qt 4.7.2 and XCode4.
>>
>> Was there some other upgrade involved?
>>
>> Andre'
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt-project.org/pipermail/qt-creator-old/attachments/20110323/8f0a82b0/attachment.html