blocks|key|1500621|text|我只是在我想要停止的地方设置了一个断点。Xcode会持久地记住断点，所以每当我使用gdb运行应用程序时，它都会在断点停止。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1500622|如果您想在断言失败时中断，在Objective-C运行时中的函数objc_exception_throw上设置断点是一个很好的地方，这实际上就是抛出异常的地方。使用Run+>+Show+>+Breakpoints窗口，双击"Double-click+for+symbol“行，然后键入名称。|1500623|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I just set a breakpoint at the place I want to stop. Xcode remembers breakpoints persistently, so any time I run the app with gdb, it'll stop at that point.

If you want to break on assertion failures, a good place to set a breakpoint is on the function objc_exception_throw, in the Objective-C runtime, which is what actually throws an exception. Use the Run > Show > Breakpoints window and double-click the "Double-click for symbol" row, then type the name.

blocks|key|1285820|text|查看条件断点：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1285821|http://www.cocoabuilder.com/archive/message/xcode/2008/10/22/25358|offset|length|1285822|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1U|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

Check out conditional breakpoints:

<a href="http://www.cocoabuilder.com/archive/message/xcode/2008/10/22/25358" rel="nofollow noreferrer">http://www.cocoabuilder.com/archive/message/xcode/2008/10/22/25358</a>

blocks|key|1285886|text|首先，将-DDEBUG添加到调试目标上的OTHER_CFLAGS；这将在构建调试构建时定义DEBUG符号。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1285887|然后在您的前缀标题中添加一个简单的assert宏：|1285888|#ifdef+DEBUG
#define+MyAssert(val)+_MyAssert(val)
#else
#define+MyAssert(val)+do+{+}+while(0)
#endif|code-block|syntax|javascript|1285889|接下来，在某个模块中创建一个_MyAssert函数：|1285890|#ifdef+DEBUG
void+_MyAssert(int+expression)
{
++++if+(expression+==+0)+{
+++++++NSLog(@"Assertion+failed!");+//+Place+breakpoint+here
++++}
}
#endif|1285891|最后，在NSLog行上创建一个断点。|1285892|entityMap^0|4|7|K|C|19|5|0|0|0|E|9|0|0|4|5|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|11|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|12|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|13|8|@$9|14|A|15|B|C]]|D|@]|E|$]]|$1|O|3|P|5|J|7|16|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|17|8|@$9|18|A|19|B|C]]|D|@]|E|$]]|$1|S|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|T|$]]

First Add <code>-DDEBUG</code> to <code>OTHER_CFLAGS</code> on your debug target; this will define the <code>DEBUG</code> symbol when building a debug build.

Then add a simple assert macro to your prefix header:

<pre><code>#ifdef DEBUG
#define MyAssert(val) _MyAssert(val)
#else
#define MyAssert(val) do { } while(0)
#endif
</code></pre>

Next create a <code>_MyAssert</code> function in a module somewhere:

<pre><code>#ifdef DEBUG
void _MyAssert(int expression)
{
 if (expression == 0) {
 NSLog(@"Assertion failed!"); // Place breakpoint here
 }
}
#endif
</code></pre>

Finally create a breakpoint on the <code>NSLog</code> line.

blocks|key|1500773|text|简单的assert()宏有问题吗？就像这样|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1500774|assert(pointerToTest+!=+nil);|code-block|syntax|javascript|1500775|如果条件不为真，将在该点停止您的进程。如果在调试器下运行，您将看到导致断言失败的调用的堆栈跟踪。如果您想在每次访问某个代码路径时都触发它，您可以这样做|1500776|assert(false);|1500777|我发现这些断言对于验证当窗口或视图从NIB中打开时所有的IBOutlets是否是非空的非常有用。|1500778|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Is there something wrong with the simple assert() macro? Something like

<pre><code>assert(pointerToTest != nil);
</code></pre>

will halt your process at that point if the condition is not true. If running under the debugger, you'll be presented with a stack trace of calls that led to the failed assertion. If you want to trigger it every time you hit a certain code path, you could do

<pre><code>assert(false);
</code></pre>

I find these assertions extremely useful for verifying that all IBOutlets are non-nil when a window or view is brought up from a NIB.

blocks|key|1500848|text|苹果开发者论坛上的一位乐于助人的人给了我在设备上运行时使用asm("trap")的提示，以及在模拟器上运行时使用asm("int3")的提示。如果在调试模式下启动程序(Option-Command-Y)，这会使程序中断到调试器。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1500849|(__builtin_trap()也会进入调试器，但之后就无法继续了。(+assert(false)使用一条消息终止程序，但不会中断调试器。)|1500850|entityMap^0|T|B|1K|B|0|1|G|11|D|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|I|$]]

A helpful person on Apple's developer forum gave me the tip to use <code>asm("trap")</code> when running on the device and <code>asm("int3")</code> when running on the simulator. This makes the program break into the debugger if you started your programm in debug mode (Option-Command-Y).

(<code>__builtin_trap()</code> also breaks into the debugger, but you can't continue afterwards. <code>assert(false)</code> terminates the program with a message, but doesn't break into the debugger.)

blocks|key|1500911|text|如果在调试中运行程序，则应用程序应在调试器到达无效断言时启动调试器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1500912|为了让它停止，正如Jens+Alfke试图说的那样，您需要启用“stop+on+Objective-C+Exceptions”(在Run菜单下)。|1500913|有关调试与发布和断言的更多信息，请阅读http://myok12.wordpress.com/2010/10/10/to-use-or-not-to-use-assertions/|offset|length|1500914|entityMap|0|LINK|mutability|MUTABLE|url|http://myok12.wordpress.com/2010/10/10/to-use-or-not-to-use-assertions/^0|0|0|J|1Z|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

If you run your program in debug, your app should launch the debugger when it reaches an invalid assertion.

For it to stop, as Jens Alfke tried to say, you need to enable "Stop on Objective-C Exceptions" (under the Run menu).

For more info about debugging vs. releasing and asserts, read <a href="http://myok12.wordpress.com/2010/10/10/to-use-or-not-to-use-assertions/" rel="nofollow">http://myok12.wordpress.com/2010/10/10/to-use-or-not-to-use-assertions/</a>

For assert macros in my iPhone project, I'm looking for a way to programmatically break into the debugger. On Windows (MSVC++), I can use __debugbreak() for this purpose. Invoking this function will stop my program, launch the debugger, and display a callstack of the line that called __debugbreak().

Is there anything similar to __debugbreak() for the iPhone? I've tried Debugger(), but that gives me a linker error.

Thanks,
Claus

Breaking into the debugger on iPhone

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

对于我的iPhone项目中的断言宏，我正在寻找一种以编程方式进入调试器的方法。在Windows (MSVC++)上，我可以使用__debugbreak()来实现这一目的。调用此函数将停止我的程序，启动调试器，并显示调用__debugbreak()的行的调用堆栈。有没有类似于iPhone的__debugbreak()？我...

问进入iPhone上的调试器
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问进入iPhone上的调试器EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问进入iPhone上的调试器
EN