Re: Setting up GDB
Re: Setting up GDB
- Subject: Re: Setting up GDB
- From: Prokash Sinha <email@hidden>
- Date: Sat, 28 Mar 2015 09:03:50 -0700
|
Thanks Phil,
The mistake I made was to take a snapshot before even trying to
configure for kernel debugging. So I can not get into a situation
where I can connect to the target using kdp protocol. And rightly
so, I should have at least pinged the target even before trying to
configure.
I will try the suggested steps you gave here.
I was hoping there should be a VHD (virtual harddisk ) that I
could traverse ( hack ) to disable the configuration I made to
plist.
Prokash
On 3/28/2015 6:48 AM, Phil Jordan wrote:
com.apple.Boot.plist will not modify nvram, but you can
specify boot args via NVRAM. Depending on your setup, that
might be more convenient.
The only way of resuming from the kernel debugger I'm aware
of is to 'continue' from lldb.
Can you ping the VM when not stuck in the debugger? If not,
this might be a routing issue - you might not be able to
directly access the VM from the host if you're in "NAT" mode
or similar.
The other thing is you're using debug=0x01 - I suggest trying
with the DB_ARP (0x40) bit set as well. This
enables ARP (address resolution protocol) even when stopped in
the kernel debugger, which might help if the VM environment is
adding a hop for whatever reason. (this shouldn't make a
difference if you're bridging to the the VM though)
Also helpful, especially during early boot, are the 0x2 and
0x08 bits for outputting printf and kprintf. The latter
requires a serial port or firewire - adding a serial port to
your VM that writes to a file should be easy to do.
phil
|
_______________________________________________
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