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

[Kuiper, Luuk]

One of my colleagues new what Archer was and we downloaded and used  a new gdb:

stdout:~"GNU gdb (GDB) 6.8.50.20090503-cvs\n"

But the slow start up is still the same.

And yes, you are right about:

> It's the time between "run" and the breakpoint triggers.

When I remove all the breakpoint, my application starts within seconds.

So, when breakpoints are set on forehand, it takes time to start.

I did some manual labour.

I took the input from file no_q_dump_helper_gdb_cmds.txt, stripped the command nummber from it. The result of that you can find  manual_input.txt.
I pasted all command until and with the -exec-continue after the -break-inserts (so unitl and with line 33 in manual_input.txt).

The output of the session you can find in manual_output.out.

I timed form the start of pasting all information in gdb until reaching my first breakpoint: 46 seconds.
The QtCreator took for that was 91 seconds.

I must say that the difference in time is a lot less than I experienced yesterday. I cannot explain that.

I did some other experiment.

I replaced the lines 30, 31 and 32 ( the setting of the break points) by the next lines:

break preselem.cxx:1053
break preselem.cxx:1060
break trackhandler.cxx:113

And than I reach my first breakpoint after only 9 seconds.

Isn't that funny?

The output of that session is in manual_output_my_style.out.


I hope this is some information you can do something with.

Greetings,

Luuk

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

On Thursday 07 May 2009 15:33:27 ext Kuiper, Luuk wrote:
> [Sure I did not. Here they are again. For what it is worth]
> 
> When starting the same executable with ddd (so gdb) I t takes 8.78 
> seconds to reach my first break point.

You log looks fine now, but I have no idea where the time difference come from.

>  > 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",enable
> > d= 
> > "y",addr="0x0000000000c0374e",func="tdl::StrMappedElement::addMappin
> > g(
> > RWCString const&, QString

It's the time between "run" and the breakpoint triggers.
There is nothing Creator does inbetween. Also, the debug symbols have been read before the "run" was issued (command 27) so I am running out of ideas.

If you have some time to waste you could run the commands from the input pane in a plain gdb session and check whether there is a single "offending" command.

> [...] what is "archer-tromey-delayed-symfile" 
> and "Project Archer"?

http://sourceware.org/gdb/wiki/ArcherBranchManagement
http://sourceware.org/gdb/wiki/ProjectArcher

It's the place where the interesting parts of gdb development seem to happen nowadays.

Andre'

_______________________________________________
Qt-creator mailing list
Qt-creator at trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator
-------------- next part --------------
A non-text attachment was scrubbed...
Name: manual_output.out
Type: application/octet-stream
Size: 18524 bytes
Desc: manual_output.out
Url : http://lists.qt-project.org/pipermail/qt-creator-old/attachments/20090508/84f9879b/attachment.obj 
-------------- 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/20090508/84f9879b/attachment.txt 
-------------- 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/20090508/84f9879b/attachment-0001.txt 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: manual_input.txt
Url: http://lists.qt-project.org/pipermail/qt-creator-old/attachments/20090508/84f9879b/attachment-0002.txt 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: manual_output_my_style.out
Type: application/octet-stream
Size: 17412 bytes
Desc: manual_output_my_style.out
Url : http://lists.qt-project.org/pipermail/qt-creator-old/attachments/20090508/84f9879b/attachment-0001.obj