很实用的技巧，便拿来试验一下。
原文是在XCode3里面设置的，so在4里面完全找不到地方。stackoverflow搜一下，找到如下方法。
菜单里Product->EditScheme->Run->EnvironmentVariables, 添加NSZombieEnabled，YES。
顺便发现方法2，Product->按住alt/option+鼠标点"Run...",之后同上。
如果你和我一样操作了，一定发现了：按下alt/option键之后菜单边了，同理，按下Ctrl键之后菜单也变了。
神奇ing！
顺便在Navigate看到一条”Fix nextissue“，（按住Ctrl）,原来XCode支持
自动修复简单错误。
试验发现只要报错信息里有fix方法的，都能用Ctrl+Command+'修复。
In the Xcode IDE two environment variables are useful for gettingfurther information on the memory allocation error EXC_BAD_ACCESSwhen using the simulator:
There variables should be unchecked when not debugging specificmemory issues, as they will cause the memory shortages in theruntime environment, and should never be enabled in a shippingapplication. This is indicated by the followingmessage:
"Data Formatters temporarily unavailable, will re-try after a'continue'. (Not safe to call dlopen at thistime.)"
Uncheck these environment variables to resolve the issue.
NSZombieEnabled=YES
MallocStackLoggingNoComp
There variables should be unchecked when not debugging specificmemory issues, as they will cause the memory shortages in theruntime environment, and should never be enabled in a shippingapplication. This is indicated by the followingmessage:
"Data Formatters temporarily unavailable, will re-try after a'continue'. (Not safe to call dlopen at thistime.)"
Uncheck these environment variables to resolve the issue.
Resolution
To set these environment variables in the XcodeIDE.
In Xcode 3.2:
- In the left pane of Xcodeexpand
- Select the application executable
-Select
- Selectthe
- At the bottom of the
-Enter
-Click
-Enter
- Close the dialogue
In Xcode 4.0:
-Select
- Select the appropriate scheme ( Run/Test) in theleft pane
- Selectthe
- At the bottom of the
-Enter
-Click
-Enter
- Close the dialogue
Recreate the fault. An error should appear in the debugger console( Run
This address is then used to query the debuggerwith
That will produce the following output:
The cause of this error is visible near the top of theblock:
In Xcode 3.2:
- In the left pane of Xcodeexpand
- Select the application executable
-Select
- Selectthe
- At the bottom of the
-Enter
-Click
-Enter
- Close the dialogue
In Xcode 4.0:
-Select
- Select the appropriate scheme ( Run/Test) in theleft pane
- Selectthe
- At the bottom of the
-Enter
-Click
-Enter
- Close the dialogue
Recreate the fault. An error should appear in the debugger console( Run
*** -[__NSArrayI release]: message sent to deallocated instance 0x4d90af0
This address is then used to query the debuggerwith
(gdb) info malloc-history 0x4d90af0 （注：只能在模拟器上使用）
That will produce the following output:
Alloc: Block address: 0x04d90af0 length: 32
Stack - pthread: 0xa0078540 number of frames: 37
0: 0x90e5a103 in malloc_zone_calloc
1: 0x5d862 in NSAllocateScannedUncolle
The cause of this error is visible near the top of theblock:
...
4: 0x127c89 in -[NSSet(NSKeyValueSorting) sortedArrayUsingDescript
扫一扫
5829
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
