1

这个问题已经过时了,因为它是针对 XCode 3 提出的。请不要认为它对 XCode 4+ 有用。=)


我的应用程序在(看似)随机事件时崩溃。所以,我想添加 NSZombieEnabled 来调试我的 iPhone 应用程序。我克隆了我的目标并将其 Info.plist 设置为与原始目标相同,并将 NSZombieEnabled 设置为 YES。

一旦我运行该应用程序,它就会崩溃并显示...

#0  0x3025db0c in ___forwarding___ ()
#1  0x30239db2 in __forwarding_prep_0___ ()
#2  0x304f5105 in NSPopAutoreleasePool ()
#3  0x308ee452 in _UIApplicationHandleEvent ()
#4  0x32031425 in PurpleEventCallback ()
#5  0x30235253 in CFRunLoopRunSpecific ()
#6  0x302343c8 in CFRunLoopRunInMode ()
#7  0x308e6209 in -[UIApplication _run] ()
#8  0x308eef81 in UIApplicationMain ()
#9  0x000023ef in main (argc=1, argv=0xbffff0bc) at /Users/tomen/Documents/MIB-Sprint4/main.m:26

这仅在 NSZombieEnabled 设置为 YES 时发生。如果未设置,应用程序只会运行(并在不同时间崩溃)

我想添加诸如“-[_NSZombie methodSignatureForSelector:]”之类的断点,但它们在调试期间被停用。我在打开和关闭“懒加载符号”的情况下尝试了两种方法。

我还尝试将我的 ~/.gdbinit 文件设置为

fb -[NSException raise]
fb -[NSAssertionHandler handleFailureInFunction:file:lineNumber:description:]
fb -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:]

#define NSZombies
# this will give you help messages.  Set to NO to turn them off.
set env MallocHelp=YES
# might also be set in launch arguments.
set env NSZombieEnabled=YES
set env NSDeallocateZombies=NO
set env MallocCheckHeapEach=100000
set env MallocCheckHeapStart=100000
set env MallocScribble=YES
set env MallocGuardEdges=YES
set env MallocCheckHeapAbort=1

set env CFZombie 5

fb -[_NSZombie init]
fb -[_NSZombie retainCount]
fb -[_NSZombie retain]
fb -[_NSZombie release]
fb -[_NSZombie autorelease]
fb -[_NSZombie methodSignatureForSelector:]
fb -[_NSZombie respondsToSelector:]
fb -[_NSZombie forwardInvocation:]
fb -[_NSZombie class]
fb -[_NSZombie dealloc]

fb szone_error

在控制台中产生这个结果:

The Debugger has exited with status 0.
[Session started at 2009-09-08 13:48:40 +0200.]
Loading program into debugger…
GNU gdb 6.3.50-20050815 (Apple version gdb-966) (Tue Mar 10 02:43:13 UTC 2009)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-apple-darwin".warning: Unable to read symbols for "/System/Library/Frameworks/UIKit.framework/UIKit" (file not found).
warning: Unable to read symbols from "UIKit" (not yet mapped into memory).
warning: Unable to read symbols for "/System/Library/Frameworks/CoreGraphics.framework/CoreGraphics" (file not found).
warning: Unable to read symbols from "CoreGraphics" (not yet mapped into memory).
Pending breakpoint 1 - "-[NSException raise]" resolved
Pending breakpoint 2 - "-[NSAssertionHandler handleFailureInFunction:file:lineNumber:description:]" resolved
Pending breakpoint 3 - "-[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:]" resolved
Pending breakpoint 14 - "szone_error" resolved
Program loaded.
sharedlibrary apply-load-rules all
Attaching to program: `/Users/tomen/Library/Application Support/iPhone Simulator/User/Applications/F77D9D82-0B34-4B8D-9076-AE883A2714F4/MIB.app/MIB', process 279.
Re-enabling shared library breakpoint 1
Re-enabling shared library breakpoint 2
Re-enabling shared library breakpoint 3
Re-enabling shared library breakpoint 14
Re-enabling shared library breakpoint 16
Re-enabling shared library breakpoint 17
Re-enabling shared library breakpoint 18
warning: Couldn't raise load state for requested objfile: "/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation" for breakpoint 1/

warning: Couldn't raise load state for requested objfile: "/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation" for breakpoint 2/

warning: Couldn't raise load state for requested objfile: "/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation" for breakpoint 3/

为什么我的断点会被停用?

4

1 回答 1

2

我也一直在尝试这种方法,结果相同。我的理解是 NSZombie 断点在 Leopard 和 Snow Leopard 中不再有效。

一些替代方案:

1) 转储 obj_msg_send 上的 eax 寄存器。我没有亲自尝试过这个,但我发现了很多关于这个主题的帖子: 如何调试仅在 iPhone 应用程序的发布目标上发生的 EXC_BAD_ACCESS?

2) 使用信息 malloc-history。在模拟器中运行良好,但我没有运气从设备中删除日志。查找已释放的解除分配的对象实例

3) 最好的办法可能是在 Instruments 中运行您的应用程序。请注意,NSZombie 模式在设备上不可用。这可能会有所帮助: iPhone 内存调试 NSZombie

于 2011-07-26T22:32:49.633 回答