 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Mac Forum / Programming / CodeWarrior / November 2005annoying bug in CW debugger
Has anyone else experienced the following problem. In the debugger, if I drag the point-of-execution pointer up a few lines to run those lines over again, and then hit Cmd-R to let the program run (until it hits a breakpoint), the program starts insistently stepping-in as if I am hitting Ctrl-T perpetually. But I am not. I am hitting Cmd-R. It is impossible to debug anything when CW insistts on stepping into everything every step of the way. It starts marching into the deepest inner depths of every single STL call, which can take hundreds of steps to exit from, when all I wanted was to run the program freely to a breakpoint...or at the very least step over such deep STL calls. This only happens when I drag the execution point to a new location. It is truly aggrivating. I basically cannot use the debugger in this fasion at all. It is totally useless. I have the most recent CW upgrade, 9.6 I think. The IDE is 5.5.5, build 1869. What is the solution to this terrible bug. How does it even occur? How does dragging the execution point correlate with the step-in command anyway? Thanks for any help. ________________________________________________________________________ Keith Wiley kwiley@cs.unm.edu http://www.unm.edu/~keithw "Yet mark his perfect self-contentment, and hence learn his lesson, that to be self-contented is to be vile and ignorant, and that to aspire is better than to be blindly and impotently happy." -- Edwin A. Abbott, Flatland ________________________________________________________________________ > Has anyone else experienced the following problem. In the debugger, if I > drag the point-of-execution pointer up a few lines to run those lines over [quoted text clipped - 8 lines] > > This only happens when I drag the execution point to a new location. Ever since upgrading to CW 9.6, I've noticed the debugger is completely busted in various ways like what you describe, but not involving dragging the execution point. Noteably I recall not being able to avoid stepping in, and having step out result effectively in a "Run", requiring me to set breakpoints by hand in order to step out of a function. Since characterizing CW problems has so often occupited so much of my time, I have stopped paying attention to these things, and instead just stuble along. For the most, I give up. So my memory of details is a little vague. I suspect the problems were with Mach-O targets but they might have been Carbon CFM targets. > It is truly aggrivating. I basically cannot use the debugger in this > fasion at all. It is totally useless. I have the most recent CW upgrade, [quoted text clipped - 3 lines] > does dragging the execution point correlate with the step-in command > anyway? Ron had mentioned that there were problem due to changes in debugging services in tiger. CW 9.6 was I think supposed to deal with some of them, but clearly not all. -Kurt > Ever since upgrading to CW 9.6, I've noticed the debugger is completely > busted in various ways like what you describe, but not involving dragging > the execution point. Noteably I recall not being able to avoid stepping in, > and having step out result effectively in a "Run", requiring me to set > breakpoints by hand in order to step out of a function. I had the same poblem (Mac OS X 10.4) and upgrading to the latest XCode provided me with the latest gdb*, which seems to work much better with CW 9.6. Thorsten * gdb is the reason why the CW debugger under Mac OS X is so bad. CW connects to a gdb process and translates its output to look like that of the "old", working CW debugger under Mac OS. >Has anyone else experienced the following problem. In the debugger, if I >drag the point-of-execution pointer up a few lines to run those lines over [quoted text clipped - 16 lines] >does dragging the execution point correlate with the step-in command >anyway? As Thorsten said you probably need to upgrade to the newer XCode tools. Ron  SignatureCodeWarrior Community Forum is a free online resource for developers to discuss CodeWarrior topics with other users and our staff -- http://www.codewarrior.com/community -- Ron Liechty - ron.liechty@freescale.com - http://www.codewarrior.com > As Thorsten said you probably need to upgrade to the newer XCode tools. I appreciate the suggestion, but I don't see a version of Xcode more recent than 2.1 (IDE 621.0, Core 620.0, ToolSupport 610.0), which I've had ever since I upgraded to Tiger. My gcc is version 4.0.0 and my gdb is version "6.1-20040303 (Apple version gdb-413)". Are those the most recent versions? Where do I get more recent versions is Apple's website only has Xcode 2.1 available? Thanks. ________________________________________________________________________ Keith Wiley kwiley@cs.unm.edu http://www.unm.edu/~keithw "Yet mark his perfect self-contentment, and hence learn his lesson, that to be self-contented is to be vile and ignorant, and that to aspire is better than to be blindly and impotently happy." -- Edwin A. Abbott, Flatland ________________________________________________________________________ You are not alone in this... I too have the latest Xcode and CW 9 updates. I'd sure love to have this working, but it doesn't so I just grit my teeth and go on... > > As Thorsten said you probably need to upgrade to the newer XCode tools. > [quoted text clipped - 15 lines] > -- Edwin A. Abbott, Flatland > ________________________________________________________________________ > You are not alone in this... I too have the latest Xcode and CW 9 > updates. If you have access to Seed stuff there is something newer, but I guess you have to pay $500/year for that privilege? I do have that access and recently updated to the latest seed but haven't needed to use the debugger much yet. However I used it a little and so far I didn't run into the problem, but I don't know whether that's just a coincidence of what operations I did. > I'd sure love to have this working, but it doesn't so I just grit my > teeth and go on... Letting go of the jaw may be a better practice, but indeed there is plenty of opportunity for practicing. ;) -Kurt >>> As Thorsten said you probably need to upgrade to the newer XCode tools. >> [quoted text clipped - 15 lines] >> -- Edwin A. Abbott, Flatland >> ________________________________________________________________________ |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.