Note that there are some explanatory texts on larger screens.

plurals
  1. POException Breakpoints - LLDB Results vs. GDB
    text
    copied!<p>I have searched for topics specifically to this question but have not found anything close to my experience. Forgive me if I have overlooked the answer. I am familiar with GDB and exception points, break points, etc... but the following test of debugging in GDB vs LDB left me without a plausible response.</p> <p><strong>Global Test Values</strong></p> <ul> <li>Xcode 4.2.1 </li> <li>New Single Window Project (Default template w/no changes)</li> <li>Arc Enabled</li> <li>Storyboard Enabled</li> </ul> <p><strong>Case 1 - GDB Debugger</strong></p> <p>Exception Breakpoint Values: </p> <ul> <li>Exception - All</li> <li>Break on - Throw</li> <li>Arguments - None</li> <li>Result - No Crash</li> </ul> <p><strong>Case 2 - LLDB Debugger</strong></p> <p>Exception Breakpoint Values: </p> <ul> <li>Exception - All</li> <li>Break on - Throw</li> <li>Arguments - None</li> <li>Result - Crash with Sigbart &amp; machine code; no discernible stack trace</li> </ul> <p><strong>Case 3 - LLDB Debugger</strong></p> <p>Exception Breakpoint Values: </p> <ul> <li>Exception - Objective-C</li> <li>Break on - Throw</li> <li>Arguments - None</li> <li>Result - No Crash</li> </ul> <p><strong>Case 4 - LLDB Debugger</strong></p> <p>Exception Breakpoint Values: </p> <ul> <li>Exception - C++</li> <li>Break on - Throw</li> <li>Arguments - None</li> <li>Result - Crash with Sigbart and machine code; no discernible stack trace</li> </ul> <p><strong>Question:</strong> Should I simply assume that selecting "Objective-C" as an Exception option is a safe way to go, or am I potentially ignoring a glaring issue? It is my understanding that as of Xcode 4.2.1, it is recommended I use LLDB and would like to. However, I am curious about the results above. </p> <p>Thanks in advance to all community responses! </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload