Hi Heyu
because i only have one machine to debug, i'm quite experienced with one
machine debugging. Here are some tips: As Rich already mentioned, always
create symbol files when you load your driver ( with kextload -s /tmp -n
mykext.kext ). Additionaly, I usually copy these symbol files to a
different volume and unmount that volume ( i recommend a usb flash stick
), because the crash usually ruins the created symbol files or doesn't
replace the old ones ( especielly if your Volume is a Journaled Volume ).
Then when your crash occurrs write down the first four or five addresses
of the stack ( you need to turn on Kernel debugging for this: sudo nvram
boot-args="debug=0x144" )! Then after you have restarted your machine,
start gdb and add the symbol files with add-symbol-file! I prefer using b
*0xstackaddr ( where stackaddr is the stack address you wrote down )
instead of x/i *0xstackaddr because x/i can sometimes fail if your kernel
extension hasn't loaded yet ( b *0xstackaddr always works )! Hope that
helped!
Greetings from Germany
Fabian Renn
At 12:39 PM +0800 5/9/05, email@hidden wrote:
Hi all:
Now I make a driver for AR5523. It is a USB 11g chip.
But it will crash the system when send message via message bulk out pipe.
only opcode is 4 will cause crash. other is not.
I cannot understand the opcode is recognize only by device.
How the USB device cause system crash?
I try it on 10.2.8 & 10.3.9, the result is same.
here is the panic log
Sun May 8 17:53:33 2005
--
+++ Lassen Sie Ihren Gedanken freien Lauf... z.B. per FreeSMS +++
GMX bietet bis zu 100 FreeSMS/Monat: http://www.gmx.net/de/go/mail
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Usb mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/usb/email@hidden
This email sent to email@hidden
