[Qt-creator] Cannot use qtc-debugging-helper.

[Kuiper, Luuk]

[Sure I did not. Here they are again. For what it is worth]

When starting the same executable with ddd (so gdb) It takes 8.78 seconds to reach my first break point.

Forgive me my ingnorance, but what is "archer-tromey-delayed-symfile" and "Projec Archer"?

Luuk

-----Original Message-----
From: qt-creator-bounces at trolltech.com [mailto:qt-creator-bounces at trolltech.com] On Behalf Of André Pönitz
Sent: 07 May 2009 14:41
To: qt-creator at trolltech.com
Subject: Re: [Qt-creator] Cannot use qtc-debugging-helper.

On Thursday 07 May 2009 13:36:55 ext Kuiper, Luuk wrote:
> Andre,
> 
> I have rebuild QtCreator after removeing the (void *) casts.
> The messages concerning that in the gdb output are gone.
> The problem is still the same. No qt debug helpers.
> 
> Still getting the message in the dbg toolbar: Debugging helpers not found.
> Can you examine in what case this message is displayed there?
> I have switched off Options -> Debugger -> Debugging Helper -> 'Debug debugging helper'.
> 
> Again a new gdb input and output file attached.

[Sure you did?]

> One thing I see is the next in the gdb output:
> 
>             13:20:34.212
> stdout:&"call (void*)__dlopen(\"/see/6.0.0/x86_64-linux/products/qt/4.4.3/qtc-debugging-helper/libgdbmacros.so.1.0.0\", 2)\n"
>             13:20:34.262
> stdout:&"No symbol \"__dlopen\" in current context.\n"
> status:Custom dumper setup: No symbol "__dlopen" in current context.
>             13:20:34.264
> stdout:22^error,msg="No symbol \"__dlopen\" in current context."
>             13:20:34.264
> 
> Is that a problem?

We try both 'dlopen' and '__dlopen'. One fails, but it's more difficult to figure out which one it will be than to let one fail.

 > Other major point is the time before the application realy starts to run:
> 
> stdout:29^done
>             13:20:34.702
> stdout:(gdb)
> status:Running requested...
>             13:23:06.824
> stdout:30^done,bkpt={number="2",type="breakpoint",disp="keep",enabled=
> "y",addr="0x0000000000c0374e",func="tdl::StrMappedElement::addMapping(
> RWCString const&, QString 
> const&)",file="src/tdn/field/preselem.cxx",fullname="/HITT/HMI/users/l
> uuk/build/main/aramis_mk2/displaylibs/src/tdn/field/preselem.cxx",line
> ="1053",times="0",original-location="\"/BUILDS/swp/luuk/build/main/ara
> mis_mk2/displaylibs/src/tdn/field/preselem.cxx\":1053"}

> input:--- token barrier ---
> input:31-exec-continue
>             13:23:06.826
> stdout:(gdb)
> status:Running...
> 
> That is almost 3 minutes.

How long does a startup using "plain" gdb take?

Also using a recent built of the archer-tromey-delayed-symfile branch of Project Archer would probably make that a minute faster.

Andre'
_______________________________________________
Qt-creator mailing list
Qt-creator at trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: no_q_dump_helper_gdb_output.txt
Url: http://lists.qt-project.org/pipermail/qt-creator-old/attachments/20090507/16bfa880/attachment.txt 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: no_q_dump_helper_gdb_cmds.txt
Url: http://lists.qt-project.org/pipermail/qt-creator-old/attachments/20090507/16bfa880/attachment-0001.txt