异常断点-LLDB结果与GDB [英] Exception Breakpoints - LLDB Results vs. GDB
问题描述
我已经搜索了专门针对该问题的主题,但没有发现任何与我的经验相近的东西.如果我忽略了答案,请原谅我.我熟悉GDB和异常点,断点等...,但是以下在GDB和LDB中进行调试的测试使我没有一个合理的答案.
全局测试值
- Xcode 4.2.1
- 新的单窗口项目(默认模板,无更改)
- 已启用电弧
- 已启用故事板
案例1-GDB调试器
异常断点值:
- 例外-全部
- 休息-投掷
- 参数-无
- 结果-没有崩溃
案例2-LLDB调试器
异常断点值:
- 例外-全部
- 休息-投掷
- 参数-无
- 结果-Sigbart&崩溃机器代码;没有可识别的堆栈跟踪
案例3-LLDB调试器
异常断点值:
- 异常-Objective-C
- 休息-投掷
- 参数-无
- 结果-没有崩溃
案例4-LLDB调试器
异常断点值:
- 异常-C ++
- 休息-投掷
- 参数-无
- 结果-Sigbart和机器代码崩溃;没有可识别的堆栈跟踪
问题:我是否应该简单地假设选择"Objective-C"作为例外"选项是一种安全的方法,还是我可能会忽略一个明显的问题?据我了解,从Xcode 4.2.1开始,建议我使用LLDB并且愿意.但是,我对以上结果感到好奇.
在此先感谢所有社区的回应!
感谢 @Mike K 的深思熟虑的建议,我得以解决我可能忽略一个明显问题的担忧.>
当我在实际设备iPhone/iPad上重现上述场景时,使用LLDB的第2种情况和第4种情况不再产生崩溃,并且应用程序按预期运行.该问题似乎仅限于模拟器.
出于后代的考虑,我对模拟器上问题的根本原因很感兴趣,但很高兴我可以按预期继续使用LLDB.
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.
Global Test Values
- Xcode 4.2.1
- New Single Window Project (Default template w/no changes)
- Arc Enabled
- Storyboard Enabled
Case 1 - GDB Debugger
Exception Breakpoint Values:
- Exception - All
- Break on - Throw
- Arguments - None
- Result - No Crash
Case 2 - LLDB Debugger
Exception Breakpoint Values:
- Exception - All
- Break on - Throw
- Arguments - None
- Result - Crash with Sigbart & machine code; no discernible stack trace
Case 3 - LLDB Debugger
Exception Breakpoint Values:
- Exception - Objective-C
- Break on - Throw
- Arguments - None
- Result - No Crash
Case 4 - LLDB Debugger
Exception Breakpoint Values:
- Exception - C++
- Break on - Throw
- Arguments - None
- Result - Crash with Sigbart and machine code; no discernible stack trace
Question: 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.
Thanks in advance to all community responses!
Thanks to the thoughtful suggestion of @Mike K, I was able to address my concern of potentially ignoring a glaring issue.
When I reproduce the above mentioned scenario on an actual device iPhone/iPad, Cases 2 and 4 using LLDB no longer produce a crash and the application runs as intended. The issue seems to be limited to the simulator.
I am interested in the root cause of the problem on the simulator for posterity's sake, but am quite happy that I can proceed using LLDB as intended.
这篇关于异常断点-LLDB结果与GDB的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!