Apple

The arguments for firewire should have the debug argument specified in hex, e.g.

sudo nvram boot-args="debug=0x146 kdp_match_name=firewire"

I believe that firewire debugging will avoid this issue as well.

On Tue, Aug 16, 2011 at 9:18 AM, David Tay <email@hidden> wrote:

Alex,

Not yet. I'll give it a try.
sudo nvram boot-args="debug=146 kdp_match_name=firewire"

Thanks,

David

On Aug 15, 2011, at 10:06 PM, David Tay wrote:

Previously (Panther - Snow Leopard), I would do the following (ethernet based connection)
1. load the kext on the target machine kextload -l -s ~/ XXXX.kext
2. start gdb on the remote machine.
3. target remote kdp on the remote machine,
4. add-symbol-file YYYY copied from the target machine.
5. set break points in the code.
6. kextstat to make sure the kext was still loaded on the target machine.
7. Command -Power on target machine
8. connect <IP addr> from remote machine gdb session.
9. continue in gdb.
10. kextload -m on target machine.

On Lion, none of the breakpoints (eg start, stop) are reached and the driver continues running. I'm using the Lion A511 kernel debug kit.

What could be happening?

Thanks,

David
_______________________________________________
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

References:
	>kext debugging in Lion broken? (From: David Tay <email@hidden>)
	>Re: kext debugging in Lion broken? (From: David Tay <email@hidden>)
	>Re: kext debugging in Lion broken? (From: Brian Bechtel <email@hidden>)