[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 97926] New: breakpoints setting to debug Qt *.ui.h files
From:       kdevelop-bugs-admin () barney ! cs ! uni-potsdam ! de
Date:       2005-01-26 10:39:47
Message-ID: 20050126113941.97926.jerzy.grebosz () ifj ! edu ! pl
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=97926         
           Summary: breakpoints setting to debug Qt *.ui.h files
           Product: kdevelop
           Version: 3.1.2
          Platform: SuSE RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: jerzy.grebosz ifj edu pl


Version:           3.1.2 (using KDE KDE 3.2.1KDE 1.2)
Installed from:    SuSE RPMsSuSE RPMs
Compiler:          g++ 3.3.3 Suse 9.1
OS:                Linux

I posted this to the forum, but I was told it is probably the bug, so I should
rather post it here.

--------- here is the description -------------
Hi! 
 
 I recently installed the kdevelop 3.1.2 
 I imported my project which I made using the older kdevelop 2.1.5 
 This is the project which uses Qt dialog windows. 
 
 Here is the problem: 
 In the new developer I can not set breakpoints in the *.ui.h files. 
 When I set them (by clicking) they are not red, but grey (even during the execution 
 of the program) and of course the program does not stop there. 
 
 In the normal *.cpp files - there is no problem, I can set 
 the breakpoints (by clicking) and they work as expected. 
 
 So why in case of the *.ui.h files - setting breakpoints does not work ??? 
 
 But I found the trick - what to do to make the grey breakpoints - active. 
 
 1. Just after running the debugger I stop it on any *.cpp breakpoints (they are OK), 
 or I just interrupt the debbugging. 
 
 2. I go to my favourite *.ui.h file and search the name of any function existing there. For example 
 
 myclass::functionB 
 
 (now I copy it: Ctrl-C) 
 
 3. I go to the debugger window, and there, in the command line, I type (using PASTE: Ctrl-V) 
 
 break myclass::functionB 
 
 
 By this trick - all grey (not active) breakpoints of this particular file 
 are becoming active (red) !!! 
 So now, if I continue the program - it stops on these breakpoints. 
 
 =============== 
 
 This is my trick, but I do not write here to be proud of it. My question is: 
 Is there any NORMAL way, that the breakpoints can be set - just like it 
 was in the old version of kdevelop? 
 
 Sincerely 
 Jurek


[prev in list] [next in list] [prev in thread] [next in thread]