Re: Debug related setup
Re: Debug related setup
- Subject: Re: Debug related setup
- From: Prokash Sinha <email@hidden>
- Date: Sun, 03 Jul 2016 08:02:43 -0700
Thanks much Brian, once again.
This will save me quite a bit of time.
The firewire cable I used could be bad, so I got a Belkin and I
will try that next.
Do you or any one would like to recommend any particular
manufacturer for firewire cable ?
-Prokash
On 07/02/2016 09:30 PM, Brian Bechtel
wrote:
(sorry, hit send accidentally).
For coredumps,
* you need debug flags to contain 0xd44 (or some smaller
subset, but that's what I use, so I don't bother to go to a
smaller set of flags)
* you need to specify the IP address of the server where
you want to save the coredump in the "_panicd_ip" boot-args
variable. If you are using the thunderbolt->firewire
connection for two machine debugging, the coredump is always
saved locally, but you still need to specify a _panicd_ip,
even if it's not used.
sudo nvram boot-args="debug=0xd44 kdp_match_name=firewire fwkdp=0x8000 _panicd_ip=1.2.3.4"
sudo shutdown -r now
On the host, you need to issue these commands
sudo mkdir /PanicDumps
sudo chown root:wheel /PanicDumps
sudo chmod 1777 /PanicDumps
sudo launchctl load -w
/System/Library/LaunchDaemons/com.apple.kdumpd.plist
this sets up the kdumpd daemon to write coredump files to
/PanicDumps.
Firewire behaves slightly differently; it writes the file
to the home directory of the account which is doing the
debugging. Mostly. Just look for the file.
|
_______________________________________________
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