Re:Re: How to contitnule this kind of kernel debug -----Does large memory affects?
Re:Re: How to contitnule this kind of kernel debug -----Does large memory affects?
- Subject: Re:Re: How to contitnule this kind of kernel debug -----Does large memory affects?
- From: searockcliff <email@hidden>
- Date: Mon, 19 Jan 2009 11:28:15 +0800 (CST)
Hi All,
I find the line of code near the panic is memcpy().
But the parameters are fine.
One important thing:
The kernel panic only occurs on Mac Pro with memory larger than 2GB, like 3GB, 4GB,9GB and so on.
If I reduce the memory used to 2GB by boot-args, the kernel panic disappears.
So my question is:
Can the Mac OS X kernel NOT handle large memory (>2GB) well?
Or the memcpy() function fails sometime on large memory?
Thanks a lot!
在2009-01-13，"Michael Smith" <email@hidden> 写道：
On Jan 12, 2009, at 4:59 PM, searockcliff wrote:
I think you are misleading.
You only need to specify the module address when you use "createsymbolfiles " to create symbol file.
It looks like you didn't do this when generating the symbols for one of the USB family modules. It's possible that you fed the kext file rather than the symbol file to gdb.
= Mike
在2009-01-12，"William Kucharski" <email@hidden> 写道：
>
>On Jan 12, 2009, at 8:32 AM, searockcliff wrote:
>
>> But why the address of the symbol IOUSBBus::IOUSBBus is 0?
>> Address 0 seems unaccessible to the CPU.
>
>Anything from a bug to improper address resolution.
>
>Remember also that when debugging modules using GDB you have to specify
>an address at which the module was loaded using kextload.
>
> William Kucharski
>
>
《大话西游外传》贺岁新作，送豪宅、送你5000元压岁钱
_______________________________________________
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