Symbolic/source level debugging is broken in kexts other than my own
Symbolic/source level debugging is broken in kexts other than my own
- Subject: Symbolic/source level debugging is broken in kexts other than my own
- From: David Lee <email@hidden>
- Date: Fri, 05 Aug 2011 18:27:40 -0400
- Thread-topic: Symbolic/source level debugging is broken in kexts other than my own
Title: Symbolic/source level debugging is broken in kexts other than my own
Hi All,
I had this feature working, but then I did something to break it, and I can't figure out what. Where I stand now is that when I display a backtrace, it displays class::method (parameter values) at file:line # for stackframes within my own driver and within the XNU core, and I can see source code and variables when I select these stack frames. But for stack frames in other kexts (IOPCIFamily.kext, for example) I see class::method () in the backtrace with no parameters or filename or line #. When I select these frames I can't see any source or symbols.
However, when GDB is starting I do see:
Reading symbols from /Users/David/FCHBADriver/build/Debug/other_kexts/com.apple.iokit.IOPCIFamily.sym...Reading symbols from /Users/David/FCHBADriver/build/Debug/other_kexts/IOPCIFamily.kext.dSYM/Contents/Resources/DWARF/IOPCIFamily...done.
done.
and similar for each of the other kexts.
I have tried puttiing .cpp files in a variety of different places with corresponding "directory" commands pointing to the folders, but I can't get anything to work now. As I said, it used to work, but I broke it somehow. Very frustrating!
David Lee
_______________________________________________
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