Re: kernel mprotecting my stack?
Re: kernel mprotecting my stack?
- Subject: Re: kernel mprotecting my stack?
- From: Garth Cummings <email@hidden>
- Date: Wed, 7 Feb 2007 09:29:37 -0800
Hi Cyrus,On Feb 6, 2007, at 5:47 PM, Cyrus Harmon wrote: I'm not sure if this is really a kernel question per se, as it's motivated by user-space operations, rather than a KEXT or what not, but I'm getting an error like so:
[Switching to thread 11 (process 5245 thread 0x5803)] 0x90004d8a in syscall () (gdb) bt #0 0x90004d8a in syscall () Cannot access memory at address 0xba01b80 Cannot access memory at address 0xba01b7c
If you're doing this bt from a two-machine kernel debugging session, that message usually means that the address is one not known to GDB because you haven't provided symbols covering that address.
If this is code in your KEXT, you need to create a symbol file for your KEXT and load that symbol file into GDB.
--gc ____________________________________________________________________ Sr. Software Engineer Apple Developer Technical Support
|
_______________________________________________
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