MallocStackLogging environment variable 无效

fisea 2017-02-20 05:50:06

在真机上联机调试，出现crash的bug，错误信息是：message sent to deallocated instance 0x1c3dcec0
于是找到真机上run起来的进程ID（404），然后打开终端工具，执行 sudo malloc_history 333 0x1c3dcec0命令。
提示是：The target process has no stack logs. Run it with the MallocStackLogging environment variable set to get stack logs.

我检查了以下环境变量的设置。MallocStackLogging=YES，MallocStackLoggingNoCompact=YES，NSZombieEnabled=YES。但是为什么没有stack logs呢？
是不是只能在模拟器上才有stack logs，如果是，那我遇到这样子的bug（message sent to deallocated instance 0x1c3dcec0）如何fix呢？
万分感谢

...全文

341 1 打赏收藏转发到动态举报

写回复

1 条回复

切换为时间正序

请发表友善的回复…

发表回复

scribbler 2017-02-21

打赏
举报

回复

可以看看stackoverflow上的处理方法 http://stackoverflow.com/questions/3851565/using-gdb-info-malloc-command-within-xcode-iphone-dev In Xcode go to Run -> Enable Guard Malloc Set environment variable MallocStackLoggingNoCompact to YES (as you already did) to make sure the logs are being written, in the debugger console you should see this message: malloc: stack logs being written into /tmp/stack-logs.xxxx.MyApp.xxxxxx.index Now you should be able to: (gdb) info malloc 0x1646b0

Advanced Apple Debugging & Reverse Engineering v0.9.5 Explore code through LLDB, Python and DTrace, to discover more about any program than you ever thought possible. Table of Contents 1. Getting Started In this chapter, you’re going to get acquainted with LLDB and investigate the process of introspecting and debugging a program. You’ll start off by introspecting a program you didn’t even write — Xcode! 2. Help & Apropos Just like any respectable developer tool, LLDB ships with a healthy amount of documentation. Knowing how to navigate through this documentation — including some of the more obscure command flags — is essential to mastering LLDB. 3. Attaching with LLDB Now that you’ve learned about the two most essential commands, help and apropos, it’s time to investigate how LLDB attaches itself to processes. You’ll learn all the different ways you can attach LLDB to processes using various options, as well as what happens behind the scenes when attaching to processes. 4. Stopping in Code Whether you’re using Swift, Objective-C, C++, C, or an entirely different language in your technology stack, you’ll need to learn how to create breakpoints. It’s easy to click on the side panel in Xcode to create a breakpoint using the GUI, but the LLDB console can give you much more control over breakpoints. 5. Expression Now that you’ve learned how to set breakpoints so the debugger will stop in your code, it’s time to get useful information out of whatever software you’re debugging. In this chapter you’ll learn about the expression command, which allows you to execute arbitrary code in the debugger. 6. Thread, Frame & Stepping Around You’ve learned how to create breakpoints, how to print and modify values, as well as how to execute code while paused in the debugger. But so far you’ve been left high and dry on how to move around in the debugger and inspect data beyond the immediate. In this chapter, you’ll learn how to move the debugger in and out of functions while LLDB is currently paused. 7. Image it’s time to explore one of the best tools for finding code of interest through the powers of LLDB. In this chapter, you’ll take a deep dive into the image command. 8. Persisting & Customizing Commands In this chapter, you’ll learn how to persist these choices through the .lldbinit file. By persisting your choices and making convenience commands for yourself, your debugging sessions will run much more smoothly and efficiently. This is also an important concept because from here on out, you’ll use the .lldbinit file on a regular basis. 9. Regex Commands In the previous chapter, you learned about the command alias command as well as how to persist commands through the lldbinit file. Unfortunately, command alias has some limitations. The LLDB command command regex acts much like command alias, except you can provide a regular expression for input which will be parsed and applied to the action part of the command. 10. Assembly Register Calling Convention Now you’ve gained a basic understanding of how to maneuver around the debugger, it’s time to take a step down the executable Jenga tower and explore the 1s and 0s that make up your source code. This section will focus on the low-level aspects of debugging. 11. Assembly & Memory In this chapter, you’ll explore how a program executes. You’ll look at a special register used to tell the processor where it should read the next instruction from, as well as how different sizes and groupings of memory can produce very different results. 12. Assembly and the Stack What does being "passed on the stack" mean exactly? It’s time to take a deeper dive into what happens when a function is called from an assembly standpoint by exploring some “stack related” registers as well as the contents in the stack. 13. Hello, Ptrace As alluded to in the introduction to this book, debugging is not entirely about just fixing stuff. Debugging is the process of gaining a better understanding of what’s happening behind the scenes. In this chapter, you’ll explore the foundation of debugging, namely, a system call responsible for a process attaching itself to another process: ptrace. 14. Dynamic Frameworks With dynamic frameworks comes a very interesting aspect of learning, debugging, and reverse engineering. Since you have the ability to load the framework at runtime, you can use LLDB to explore and execute code at runtime, which is great for spelunking in both public and private frameworks. 15. Hooking & Executing Code with dlopen & dlsym It’s time to learn about the complementary skills of developing with these frameworks. In this chapter, you’re going to learn about methods and strategies to “hook” into Swift and C code as well as execute methods you wouldn’t normally have access to. 16. Exploring and Method Swizzling Objective-C Frameworks You’ll cap off this round of dynamic framework exploration by digging into Objective-C frameworks using the Objective-C runtime to hook and execute methods of interest. 17. Hello Script Bridging Next up in the tradeoff between convenience and complexity is LLDB’s script bridging. With script bridging, you can do nearly anything you like. Script bridging is a Python interface LLDB uses to help extend the debugger to accomplish your wildest debugging dreams. 18. Debugging Script Bridging You need a methodical way to figure out what went wrong in your LLDB script so you don’t pull your hair out. In this chapter, you’ll explore how to inspect your LLDB Python scripts using the Python pdb module, which is used for debugging Python scripts. 19. Script Bridging Classes and Hierarchy You’ve learned the essentials of working with LLDB’s Python module, as well as how to correct any errors using Python’s PDB debugging module. Now you’ll explore the main players within the lldb Python module for a good overview of the main parts. In this chapter, you’ll add some arguments to this script and deal with some annoying edge cases, such handling commands differently between Objective-C and Swift. 20. Script Bridging with Options & Arguments When you’re creating a custom debugging command, you’ll often want to slightly tweak functionality based upon options or arguments supplied to your command. A custom LLDB command that can do a job only one way is a boring one-trick pony. In this chapter, you’ll explore how to pass optional parameters (aka options) as well as arguments (parameters which are expected) to your custom command to alter functionality or logic in your custom LLDB scripts. 21. Script Bridging with SBValue & Memory So far, when evaluating JIT code (i.e. Objective-C, Swift, C, etc. code that’s executed through your Python script), you’ve used a small set of APIs to evaluate the code. It’s time to talk about a new class in the lldb Python module, SBValue, and how it can simplify the parsing of JIT code output. 22. SB Examples, Improved Lookup For the rest of the chapters in this section, you'll focus on Python scripts. As alluded to in the previous chapter, the image lookup -rn command is on its way out. When you finish this chapter, you’ll have a new script named "lookup" which queries in a much cleaner way. 23. SB Examples, Resymbolicating a Stripped ObjC Binary When LLDB comes up against a stripped executable (an executable devoid of DWARF debugging information), LLDB won’t have the symbol information to give you the stack trace. Instead, LLDB will generate a synthetic name for a method it recognizes as a method, but doesn’t know what to call it. In this chapter, you’ll build an LLDB script that will resymbolicate stripped Objective-C functions in a stack trace. 24. SB Examples, Malloc Logging For the final chapter in this section, you’ll go through the same steps I myself took to understand how the MallocStackLogging environment variable is used to get the stack trace when an object is created. From there, you’ll create a custom LLDB command which gives you the stack trace of when an object was allocated or deallocated in memory — even after the stack trace is long gone from the debugger. 25. Hello, DTrace You’ll explore a very small section of what DTrace is capable of doing by tracing Objective-C code in already compiled applications. Using DTrace to observe iOS frameworks (like UIKit) can give you an incredible insight into how the authors designed their code. 26. Intermediate DTrace This chapter will act as a grab-bag of more DTrace fundamentals, destructive actions (yay!), as well as how to use DTrace with Swift. In this chapter, you'll learn additional ways DTrace can profile code, as well as how to augment existing code without laying a finger on the actual executable itself. 27. DTrace vs objc_msgSend In this chapter, you'll use DTrace to hook objc_msgSend's entry probe and pull out the class name along with the Objective-C selector for that class. By the end of this chapter, you'll have LLDB generating a DTrace script which only generates tracing info for code implemented within the main executable that calls objc_msgSend.

在XCode，4以上版本中，设置NSZombieEnabled和MallocStackLogging 1.点击XCode的Product菜单，选择Edit Scheme...选项 2.选择左侧的Run...,右边点击Arguments 3.在Environment Variables栏里，添加NSZombieEnabled，value为YES；再添加MallocStackLoggi...

Because of taking some days to remove the environment setting, just briefly record the process in this article. Here list some method for trace it. 1. To check .bash in home directory. 2. T

刚换过的工作空间，在搭建maven工程后，进行clean或者install操作时，控制台会报如下错误： -Dmaven.multiModuleProjectDirectory system property is not set. Check $M2_HOME environment variable and mvn script match. 解决方案：之后会弹出

第一次使用Maven ，在eclipse中执行pom.xml文件的时候报错。 -Dmaven.multiModuleProjectDirectory system propery is not set.Check $M2_HOME environment variable and mvn script match. 参考网上的解决方案：设一个环境变量M2_HOME指向你的maven安装目...

29,027

社区成员

12,466

社区内容

发帖

与我相关

我的任务

社区管理员

加入社区

近7日
近30日
至今

加载中

查看更多榜单

社区公告

暂无公告

试试用AI创作助手写篇文章吧

+ 用AI写文章