I already did. With only the filename it is fast. With the whole path it is slower.
So, with '-break-insert -f' you see the same effects as with 'break'. Luuk -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of André Pönitz Sent: 08 May 2009 12:14 To: [email protected] Subject: Re: [Qt-creator] Cannot use qtc-debugging-helper. On Friday 08 May 2009 11:50:12 ext Kuiper, Luuk wrote: > In addition to my previous mail: > > When I use > > break > /HITT/HMI/users/luuk/build/main/aramis_mk2/displaylibs/src/tdn/field/p > reselem.cxx:1053 break > /HITT/HMI/users/luuk/build/main/aramis_mk2/displaylibs/src/tdn/field/p > reselem.cxx:1060 break > /BUILDS/swp/luuk/build/main/aramis_mk2/displaylibs/src/tdn/track/track > handler.cxx:113 > > In stead of > > break preselem.cxx:1053 > break preselem.cxx:1060 > break trackhandler.cxx:113 > > Then it takes also 40 seconds to reach my first break points. > > So, it seems to that it has something to do with finding the source files. That's _really_ interesting. Could you please have a look whether the path effect is the same for '-break-insert -f'? Andre' PS: You can leave in the "command numbers" when pasting the input. It acts as the "token" part for the MI parser and is syntactical legal there. _______________________________________________ Qt-creator mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-creator _______________________________________________ Qt-creator mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-creator
