Comments on: Introduction to Xcode’s Debugger http://meandmark.com/blog/2006/12/introduction-to-xcodes-debugger/ Sat, 04 Feb 2012 20:06:57 +0000 hourly 1 http://wordpress.org/?v=3.1 By: Tony http://meandmark.com/blog/2006/12/introduction-to-xcodes-debugger/comment-page-1/#comment-123 Tony Fri, 04 Sep 2009 03:49:18 +0000 http://meandmark.com/blog/?p=31#comment-123 Another thing I love about the debugger that wasn't mentioned is that when the program is stopped at a breakpoint, and you are stepping thru the code, you can hover the cursor over variables to get an instant popup that shows their type and value. Much faster way to check values than scrolling thru the Variable list. Another thing I love about the debugger that wasn't mentioned is that when the program is stopped at a breakpoint, and you are stepping thru the code, you can hover the cursor over variables to get an instant popup that shows their type and value. Much faster way to check values than scrolling thru the Variable list.

]]> By: Nathaniel Palmer http://meandmark.com/blog/2006/12/introduction-to-xcodes-debugger/comment-page-1/#comment-113 Nathaniel Palmer Sun, 21 Jun 2009 17:08:14 +0000 http://meandmark.com/blog/?p=31#comment-113 Very helpful. Thanks. Didn't realize that "loading symbols lazily" could cause so much trouble. Very helpful. Thanks. Didn't realize that "loading symbols lazily" could cause so much trouble.

]]> By: Mark Reid http://meandmark.com/blog/2006/12/introduction-to-xcodes-debugger/comment-page-1/#comment-97 Mark Reid Mon, 26 Jan 2009 20:48:00 +0000 http://meandmark.com/blog/?p=31#comment-97 Thanks for this quick guide. It really helped me to understand what the debugger can do to help me out of bugs in my code. If only I knew this a while ago. :-D Thanks for this quick guide. It really helped me to understand what the debugger can do to help me out of bugs in my code. If only I knew this a while ago. :-D

]]> By: Mark http://meandmark.com/blog/2006/12/introduction-to-xcodes-debugger/comment-page-1/#comment-67 Mark Fri, 29 Aug 2008 19:36:00 +0000 http://meandmark.com/blog/?p=31#comment-67 If you set a breakpoint on a line of code that doesn't do anything, such as a variable declaration, the debugger won't stop at the breakpoint. The debugger will stop at the next line of code that does something. I did a test on a small command-line C++ program. When I set a breakpoint on a variable declaration, the debugger stopped at the next line of code instead of the line where I set the breakpoint.<br/><br/>If you set a breakpoint on a line of code that does something, such as a cout statement, and the debugger isn't stopping at breakpoints, make sure you have turned off code optimization. Code optimization can eliminate lines of code. The Optimization Level build setting is in the GCC Code Generation collection.<br/><br/>If you turn off code optimization and the debugger is skipping your breakpoint, open Xcode's preferences window by choosing Xcode > Preferences. In the Debugging section, deselect the Load Symbols Lazily checkbox. Loading symbols lazily is a common cause of breakpoints being skipped. If you set a breakpoint on a line of code that doesn't do anything, such as a variable declaration, the debugger won't stop at the breakpoint. The debugger will stop at the next line of code that does something. I did a test on a small command-line C++ program. When I set a breakpoint on a variable declaration, the debugger stopped at the next line of code instead of the line where I set the breakpoint.

If you set a breakpoint on a line of code that does something, such as a cout statement, and the debugger isn't stopping at breakpoints, make sure you have turned off code optimization. Code optimization can eliminate lines of code. The Optimization Level build setting is in the GCC Code Generation collection.

If you turn off code optimization and the debugger is skipping your breakpoint, open Xcode's preferences window by choosing Xcode > Preferences. In the Debugging section, deselect the Load Symbols Lazily checkbox. Loading symbols lazily is a common cause of breakpoints being skipped.

]]> By: Anonymous http://meandmark.com/blog/2006/12/introduction-to-xcodes-debugger/comment-page-1/#comment-66 Anonymous Fri, 29 Aug 2008 13:00:00 +0000 http://meandmark.com/blog/?p=31#comment-66 Hello,<br/>Thanks for the quick guide.<br/>When I debug a small c++ program in xcode 3, I can't get the debugger to stop on my first breakpoint; it just goes passed it to the first cout statement. However, when I debug the same code in Visual C++ 2008 Express it stops on every breakpoint.<br/>Is this how xcode is intended to work? Or is it a bug in the debugger?<br/>Thanks Mark. Hello,
Thanks for the quick guide.
When I debug a small c++ program in xcode 3, I can’t get the debugger to stop on my first breakpoint; it just goes passed it to the first cout statement. However, when I debug the same code in Visual C++ 2008 Express it stops on every breakpoint.
Is this how xcode is intended to work? Or is it a bug in the debugger?
Thanks Mark.

]]> By: Anonymous http://meandmark.com/blog/2006/12/introduction-to-xcodes-debugger/comment-page-1/#comment-62 Anonymous Fri, 22 Aug 2008 15:54:00 +0000 http://meandmark.com/blog/?p=31#comment-62 This is very helpful!! This is very helpful!!

]]> By: Anonymous http://meandmark.com/blog/2006/12/introduction-to-xcodes-debugger/comment-page-1/#comment-31 Anonymous Wed, 23 Jan 2008 14:27:00 +0000 http://meandmark.com/blog/?p=31#comment-31 Thanks!<br/><br/>Nice guide Thanks!

Nice guide

]]>
Warning: Cannot modify header information - headers already sent by (output started at /home/szymczyk/public_html/blog/wp-includes/feed-rss2-comments.php:10) in /home/szymczyk/public_html/blog/wp-includes/pluggable.php on line 897