Re: [Qt-creator] debugging VS steps: 30 seconds
Hi, > Can I just build the latest git version also? yes, sure, it is already in master (will occur somewhat delayed in the public repository, I believe). Friedemann ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] debugging VS steps: 30 seconds
Nope, didn't work...how does cherry-picking work? I'm not familiar with that... From: Boy Lenssen Sent: woensdag 15 juli 2009 17:01 To: 'qt-creator@trolltech.com' Subject: RE: [Qt-creator] debugging VS steps: 30 seconds Can I just build the latest git version also? From: Friedemann Kleint [mailto:friedemann.kle...@nokia.com] Sent: woensdag 15 juli 2009 16:54 To: qt-creator@trolltech.com Subject: Re: [Qt-creator] debugging VS steps: 30 seconds Hi, > Here it is Ah, it was considering C++ exceptions to be a crash, too, which I fixed with b2ec44ba907bdcf2b6e15b2d1641af108b2956fa. This can be cherry-picked into a 1.2.1 branch, should you have one. Friedemann ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] debugging VS steps: 30 seconds
Can I just build the latest git version also? From: Friedemann Kleint [mailto:friedemann.kle...@nokia.com] Sent: woensdag 15 juli 2009 16:54 To: qt-creator@trolltech.com Subject: Re: [Qt-creator] debugging VS steps: 30 seconds Hi, > Here it is Ah, it was considering C++ exceptions to be a crash, too, which I fixed with b2ec44ba907bdcf2b6e15b2d1641af108b2956fa. This can be cherry-picked into a 1.2.1 branch, should you have one. Friedemann ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] debugging VS steps: 30 seconds
Hi, > Here it is Ah, it was considering C++ exceptions to be a crash, too, which I fixed with b2ec44ba907bdcf2b6e15b2d1641af108b2956fa. This can be cherry-picked into a 1.2.1 branch, should you have one. Friedemann ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] debugging VS steps: 30 seconds
Here it is From: Friedemann Kleint [mailto:friedemann.kle...@nokia.com] Sent: woensdag 15 juli 2009 16:23 To: qt-creator@trolltech.com Subject: Re: [Qt-creator] debugging VS steps: 30 seconds Hi, >Ok, something funny happened: I had some watchers for variables that were out >of scope(because they were there from previous runs and breakpoint were hit >in other function). I removed them to make a clean debugger output and tried >it again and now it works perfectly! Aha, thanks a lot for figuring this out! Not sure why this takes ages, maybe it is trying to resolve a symbol. Anyways. > But now I still have the problem that I don't see Qt type values (like > QString). I just says 'class QSTring'. I've installed Qt 4.5.2 and rebuild > the debugging helpers...no data...does this have to do with the disabling > dumpers due to debuggee crash message? Yes, it seems there is an unknown exception somewhere. Could you post the full log? Friedemann input:--- token barrier --- debug:NO GDB PROCESS RUNNING, CMD IGNORED: -stack-list-arguments 2 0 0 debug:NO GDB PROCESS RUNNING, CMD IGNORED: -stack-list-locals 2 debug:SWITCHING OFF DUMPER DEBUGGING debug:NO GDB PROCESS RUNNING, CMD IGNORED: set unwindonsignal on status:Starting Debugger status:Starting Debugger cdb:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 cdb:Copyright (c) Microsoft Corporation. All rights reserved. cdb: cdb:CommandLine: .exe cdb: cdb:Starting directory: cdb: status:Running... status:Debugger running cdb:Symbol search path is: cdb: cdb:*** Invalid *** cdb: warning: warning:* Symbol loading may be unreliable without a symbol search path. * warning:* Use .symfix to have the debugger choose a symbol path. * warning:* After setting your symbol path, use .reload to refresh symbol locations. * warning: warning: cdb:Executable search path is: cdb: cdb:ModLoad: 0040 02a05000 .exe cdb: status:Running... cdb:ModLoad: 7c90 7c9b2000 ntdll.dll cdb: cdb:ModLoad: 7c80 7c8f6000 C:\WINDOWS\system32\kernel32.dll cdb: cdb:ModLoad: 7e41 7e4a1000 C:\WINDOWS\system32\USER32.dll cdb: cdb:ModLoad: 77f1 77f59000 C:\WINDOWS\system32\GDI32.dll cdb: cdb:ModLoad: 7300 73026000 C:\WINDOWS\system32\WINSPOOL.DRV cdb: cdb:ModLoad: 77dd 77e6b000 C:\WINDOWS\system32\ADVAPI32.dll cdb: cdb:ModLoad: 77e7 77f02000 C:\WINDOWS\system32\RPCRT4.dll cdb: cdb:ModLoad: 77fe 77ff1000 C:\WINDOWS\system32\Secur32.dll cdb: cdb:ModLoad: 77c1 77c68000 C:\WINDOWS\system32\msvcrt.dll cdb: warning:*** WARNING: Unable to verify checksum for warning: warning:.dll warning: warning: warning: cdb:ModLoad: 1000 10015000 .dll cdb: cdb:ModLoad: 74ad 74ad8000 C:\WINDOWS\system32\POWRPROF.dll cdb: cdb:ModLoad: 7792 77a13000 C:\WINDOWS\system32\SETUPAPI.dll cdb: cdb:ModLoad: 0034 0039d000 .dll cdb: cdb:ModLoad: 5ed0 5edcc000 C:\WINDOWS\system32\OPENGL32.dll cdb: cdb:ModLoad: 68b2 68b4 C:\WINDOWS\system32\GLU32.dll cdb: cdb:ModLoad: 7376 737ab000 C:\WINDOWS\system32\DDRAW.dll cdb: cdb:ModLoad: 73bc 73bc6000 C:\WINDOWS\system32\DCIMAN32.dll cdb: cdb:ModLoad: 77c0 77c08000 C:\WINDOWS\system32\VERSION.dll cdb: cdb:ModLoad: 58f2 58f8 C:\WINDOWS\system32\irprops.cpl cdb: cdb:ModLoad: 72a9 72ad8000 C:\WINDOWS\system32\DEVMGR.DLL cdb: cdb:ModLoad: 71b2 71b32000 C:\WINDOWS\system32\MPR.dll cdb: cdb:ModLoad: 774e 7761d000 C:\WINDOWS\system32\ole32.dll cdb: cdb:ModLoad: 7c9c 7d1d7000 C:\WINDOWS\system32\SHELL32.dll cdb: cdb:ModLoad: 77f6 77fd6000 C:\WINDOWS\system32\SHLWAPI.dll cdb: cdb:ModLoad: 76d3 76d34000 C:\WINDOWS\system32\WMI.dll cdb: cdb:ModLoad: 71ad 71ad9000 C:\WINDOWS\system32\WSOCK32.dll cdb: cdb:ModLoad: 71ab 71ac7000 C:\WINDOWS\system32\WS2_32.dll cdb: cdb:ModLoad: 71aa 71aa8000 C:\WINDOWS\system32\WS2HELP.dll cdb: cdb:ModLoad: 46ff 47004000 C:\WINDOWS\system32\Wlanapi.dll cdb: cdb:ModLoad: 7712 771ab000 C:\WINDOWS\system32\OLEAUT32.dll cdb: cdb:ModLoad: 7303 7304 C:\WINDOWS\system32\WZCSAPI.DLL cdb: cdb:ModLoad: 76e8 76e8e000 C:\WINDOWS\system32\rtutils.dll cdb: warning:*** WARNING: Unable to verify checksum for warning: warning:.dll warning: warning: warning: cdb:ModLoad: 003b 003bf000 .dll cdb: cdb:ModLoad: 76b4 76b6d000 C:\WINDOWS\system32\WINMM.dll cdb: cdb:ModLoad: 003c 003d1000 .dll cdb: cdb:ModLoad: 02a1 03ae1000 C:\Qt\4.5.2\bin\QtWebKitd4.dll cdb: status:Loading the custom dumper library 'C:\Qt\4.5.2\qtc-debugging-helper\debug\gdbmacros.dll' (injection) ... cdb:ModLoad: 03c0 03c73000 C:\Qt\4.5.2\bin\phonond4.dll cdb: cdb:ModLoad: 6500 6
Re: [Qt-creator] debugging VS steps: 30 seconds
Hi, >Ok, something funny happened: I had some watchers for variables that were out >of scope(because they were there from previous runs and breakpoint were hit >in other function). I removed them to make a clean debugger output and tried >it again and now it works perfectly! Aha, thanks a lot for figuring this out! Not sure why this takes ages, maybe it is trying to resolve a symbol. Anyways. > But now I still have the problem that I don’t see Qt type values (like > QString). I just says ‘class QSTring’. I’ve installed Qt 4.5.2 and rebuild > the debugging helpers…no data…does this have to do with the disabling > dumpers due to debuggee crash message? Yes, it seems there is an unknown exception somewhere. Could you post the full log? Friedemann ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] debugging VS steps: 30 seconds
But now I still have the problem that I don't see Qt type values (like QString). I just says 'class QSTring'. I've installed Qt 4.5.2 and rebuild the debugging helpers...no data...does this have to do with the disabling dumpers due to debuggee crash message? From: Friedemann Kleint [mailto:friedemann.kle...@nokia.com] Sent: woensdag 15 juli 2009 15:32 To: qt-creator@trolltech.com Subject: Re: [Qt-creator] debugging VS steps: 30 seconds Hi, > Ok, works on my colleague's system...so I'll have to find another cause... That's what we are seeing too..on some system it mysteriously works, on some, it doesn't. Our initial guess was that it breaks on 64bit systems using 32bit Qt Creator, but statistics proved it wrong. Any clue would be appreciated. > dumper:Disabling dumpers due to debuggee crash... Could you post the full log? Thanks, Friedemann -- Friedemann Kleint Nokia, Qt Software ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] debugging VS steps: 30 seconds
Ok, something funny happened: I had some watchers for variables that were out of scope(because they were there from previous runs and breakpoint were hit in other function). I removed them to make a clean debugger output and tried it again and now it works perfectly! I've added (a fake one) again to the watcher before starting the debugging which expression is out of scope and it was slow again. I removed it while in debugging mode from the watcher window and now it works like a charm! From: Friedemann Kleint [mailto:friedemann.kle...@nokia.com] Sent: woensdag 15 juli 2009 15:32 To: qt-creator@trolltech.com Subject: Re: [Qt-creator] debugging VS steps: 30 seconds Hi, > Ok, works on my colleague's system...so I'll have to find another cause... That's what we are seeing too..on some system it mysteriously works, on some, it doesn't. Our initial guess was that it breaks on 64bit systems using 32bit Qt Creator, but statistics proved it wrong. Any clue would be appreciated. > dumper:Disabling dumpers due to debuggee crash... Could you post the full log? Thanks, Friedemann -- Friedemann Kleint Nokia, Qt Software ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] debugging VS steps: 30 seconds
Hi, > Ok, works on my colleague’s system…so I’ll have to find another cause… That's what we are seeing too..on some system it mysteriously works, on some, it doesn't. Our initial guess was that it breaks on 64bit systems using 32bit Qt Creator, but statistics proved it wrong. Any clue would be appreciated. > dumper:Disabling dumpers due to debuggee crash... Could you post the full log? Thanks, Friedemann -- Friedemann Kleint Nokia, Qt Software ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] debugging VS steps: 30 seconds
Ok, works on my colleague's system...so I'll have to find another cause... I get errors like: cdb:Symbol search path is: cdb: cdb:*** Invalid *** cdb: and dumper:Disabling dumpers due to debuggee crash... From: Boy Lenssen [mailto:boy.lens...@esaote.nl] Sent: dinsdag 14 juli 2009 16:48 To: qt-creator@trolltech.com Subject: Re: [Qt-creator] debugging VS steps: 30 seconds Hi, I still hadn't been able to solve this problem. Also turning debugging helpers off doesn't make it faster. My next step is to try it on a colleague's system to see if it seems to be working correctly there... I've been building latest git repositories and tried the new release 1.2.1 today... From: Boy Lenssen [mailto:boy.lens...@esaote.nl] Sent: donderdag 9 juli 2009 10:11 To: qt-creator@trolltech.com Subject: Re: [Qt-creator] debugging VS steps: 30 seconds Ok, thanks for the information! You mean 'turning the debugging helpers off' or 'tuning the debugging helpers'? I guess the first one, otherwise I would like to know how to tune them ;) From: Friedemann Kleint [mailto:friedemann.kle...@nokia.com] Sent: donderdag 9 juli 2009 9:57 To: qt-creator@trolltech.com Subject: Re: [Qt-creator] debugging VS steps: 30 seconds Hi, > I said before that I had problems with seeing Qt types values, that seems > to be solved now. But I still have the problem that every step (or when I > hit a breakpoint) the whole program hangs for about 30 seconds. > > It worked faster before. I'm not sure if it is just me (and I need to > reinstall my system or something :s ) or that this is normal for now and > work-in-progress. Do other people have this issue? No, the system is not (necessarily) to blame heretechnically, this phenomenon is caused by the debugger helpers hitting on an uninitialized variable. For example: QString s1 = "foo"; fiddle(s1); QString s2 = "bar"; At the breakpoint, the debugger already sees s2 in the stack frame and tries to display it using the Debugger helpers. As it is not yet initialized, the helper can cause memory access violations, which make it slow (particularly with CDB). We are working on the issue, but have not really found a good solution yet. Turning the debugger helpers will always make it faster. Regards. Friedemann -- Friedemann Kleint Nokia, Qt Software ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] debugging VS steps: 30 seconds
Hi, I still hadn't been able to solve this problem. Also turning debugging helpers off doesn't make it faster. My next step is to try it on a colleague's system to see if it seems to be working correctly there... I've been building latest git repositories and tried the new release 1.2.1 today... From: Boy Lenssen [mailto:boy.lens...@esaote.nl] Sent: donderdag 9 juli 2009 10:11 To: qt-creator@trolltech.com Subject: Re: [Qt-creator] debugging VS steps: 30 seconds Ok, thanks for the information! You mean 'turning the debugging helpers off' or 'tuning the debugging helpers'? I guess the first one, otherwise I would like to know how to tune them ;) From: Friedemann Kleint [mailto:friedemann.kle...@nokia.com] Sent: donderdag 9 juli 2009 9:57 To: qt-creator@trolltech.com Subject: Re: [Qt-creator] debugging VS steps: 30 seconds Hi, > I said before that I had problems with seeing Qt types values, that seems > to be solved now. But I still have the problem that every step (or when I > hit a breakpoint) the whole program hangs for about 30 seconds. > > It worked faster before. I'm not sure if it is just me (and I need to > reinstall my system or something :s ) or that this is normal for now and > work-in-progress. Do other people have this issue? No, the system is not (necessarily) to blame heretechnically, this phenomenon is caused by the debugger helpers hitting on an uninitialized variable. For example: QString s1 = "foo"; fiddle(s1); QString s2 = "bar"; At the breakpoint, the debugger already sees s2 in the stack frame and tries to display it using the Debugger helpers. As it is not yet initialized, the helper can cause memory access violations, which make it slow (particularly with CDB). We are working on the issue, but have not really found a good solution yet. Turning the debugger helpers will always make it faster. Regards. Friedemann -- Friedemann Kleint Nokia, Qt Software ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] debugging VS steps: 30 seconds
Ok, thanks for the information! You mean 'turning the debugging helpers off' or 'tuning the debugging helpers'? I guess the first one, otherwise I would like to know how to tune them ;) From: Friedemann Kleint [mailto:friedemann.kle...@nokia.com] Sent: donderdag 9 juli 2009 9:57 To: qt-creator@trolltech.com Subject: Re: [Qt-creator] debugging VS steps: 30 seconds Hi, > I said before that I had problems with seeing Qt types values, that seems > to be solved now. But I still have the problem that every step (or when I > hit a breakpoint) the whole program hangs for about 30 seconds. > > It worked faster before. I'm not sure if it is just me (and I need to > reinstall my system or something :s ) or that this is normal for now and > work-in-progress. Do other people have this issue? No, the system is not (necessarily) to blame heretechnically, this phenomenon is caused by the debugger helpers hitting on an uninitialized variable. For example: QString s1 = "foo"; fiddle(s1); QString s2 = "bar"; At the breakpoint, the debugger already sees s2 in the stack frame and tries to display it using the Debugger helpers. As it is not yet initialized, the helper can cause memory access violations, which make it slow (particularly with CDB). We are working on the issue, but have not really found a good solution yet. Turning the debugger helpers will always make it faster. Regards. Friedemann -- Friedemann Kleint Nokia, Qt Software ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] debugging VS steps: 30 seconds
Hi, > I said before that I had problems with seeing Qt types values, that seems > to be solved now. But I still have the problem that every step (or when I > hit a breakpoint) the whole program hangs for about 30 seconds. > > It worked faster before. I’m not sure if it is just me (and I need to > reinstall my system or something :s ) or that this is normal for now and > work-in-progress. Do other people have this issue? No, the system is not (necessarily) to blame heretechnically, this phenomenon is caused by the debugger helpers hitting on an uninitialized variable. For example: QString s1 = "foo"; fiddle(s1); QString s2 = "bar"; At the breakpoint, the debugger already sees s2 in the stack frame and tries to display it using the Debugger helpers. As it is not yet initialized, the helper can cause memory access violations, which make it slow (particularly with CDB). We are working on the issue, but have not really found a good solution yet. Turning the debugger helpers will always make it faster. Regards. Friedemann -- Friedemann Kleint Nokia, Qt Software ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
[Qt-creator] debugging VS steps: 30 seconds
Using Win XP SP3, repository build Qt Creator Hi, I said before that I had problems with seeing Qt types values, that seems to be solved now. But I still have the problem that every step (or when I hit a breakpoint) the whole program hangs for about 30 seconds. It worked faster before. I'm not sure if it is just me (and I need to reinstall my system or something :s ) or that this is normal for now and work-in-progress. Do other people have this issue? ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
