Re: Deadlock in open() syscall
Re: Deadlock in open() syscall
- Subject: Re: Deadlock in open() syscall
- From: Anatol Pomozov <email@hidden>
- Date: Thu, 04 Aug 2011 16:52:37 -0700
Hi
Here is the answer to my question about kext symbols. When I have a deadlock in my kext I run following command to make a stackshot and symbolize it:
$ sudo /usr/libexec/stackshot -i -f stackshot.untxt && sudo /usr/sbin/symstacks.rb -f stackshot.untxt -w stackshot.txt && sudo chown YOUR_USER stackshot.*
It symbolizes kernel and user-space programs, but not my kext where the deadlock happens. "atos" with -l parameter does not help here.
To symbolize kext I was needed to load my kext with "-s" parameter like this one
$ sudo kextutil /System/Library/Extensions/fuse4x.kext/ -s ~/tmp/
This generates debug symbols for loaded kext. See "man kextutil" section "Generating Debug Symbols When Loading". After that I was able to symbolize my kext stacktrace by
$ atos -o KEXT_SYMBOLS.sym -f STACKTRACE_FILE
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden