• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Debuggin XNU build
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Debuggin XNU build

  • Subject: Re: Debuggin XNU build
  • From: Brian Bechtel <email@hidden>
  • Date: Tue, 07 Apr 2015 09:22:41 -0700
VMware maintains the nvram variables in the virtual machine bundle, in the *nvram file inside the bundle.  Running in the vm, you can set the boot-args in a working partition and then boot to your test partition, or boot single user and set the nvram values there.  The typical value would be
  sudo nvram boot-args="debug=0x146"
as described in technote 2063 <https://developer.apple.com/library/mac/technotes/tn2063/_index.html> (which is heavily out of date, but still contains useful information.)

You can also use the "gdb-server" command; see https://twitter.com/comex/status/477650961448439808 where Shantonu Sen comments
you have to use the target definitions file at http://llvm.org/svn/llvm-project/lldb/trunk/examples/python/ …

Also, I found this little shell script somewhere on the Intarweb which sends an NMI to your VM.  Keep a copy inside the vmwarevm bundle.

#!/bin/bash


DIR=$(dirname $0)


/Applications/VMware\ Fusion.app/Contents/Library/vmrun suspend $DIR/*.vmx

perl -i -pe 's/(?<=pendingNMI\x00{4})\x00/\x01/' *.vmss

/Applications/VMware\ Fusion.app/Contents/Library/vmrun start $DIR/*.vmx



On Wed, Apr 1, 2015 at 8:41 PM, Prokash Sinha <email@hidden> wrote:
Folks,

Here is another problem I'm stuck with.

On 10.10 I have the corresponding xnu source that I can now build ( both DEBUG and RELEASE). I uses Fusion, so taking snapshot of the running VM instance is not a problem, and I wanted to drop the kernel.debug to /Systems/Library/Kernel directory, named it as kernel, and boot from there.

Since the KDP based LLDB is working when I try to connect from the host while I'm running the original OS version ( with or without the corresponding Kernel Debug Kit), I was hoping that in case of a continuous panic while trying to boot, I should be able to connect from the host.

But the problem is that while the boot messages comes to the screen, it tells that both ip and mac addresses are 0s. Like 0.0.0.0 and 00:00:00:00:00:00. And I can not connect. I looked the debug.c and kdp.c code, there seem to be some variables related to ip etc., that are being set to 0s as default. Not sure if I could hard code them based on what have from the original setup, and that would work or not.

If not, then how could I setup KDB/DDB using either nvram or using the com.apple.Boot.plist. I know this should give me just the single VM debugging !!

Would love to see if I could do Host/Target with KDP based debugging !

Any suggestion, please ?

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

 _______________________________________________
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
  • Follow-Ups:
    • Re: Debuggin XNU build
      • From: Prokash Sinha <email@hidden>
References: 
 >Debuggin XNU build (From: Prokash Sinha <email@hidden>)

  • Prev by Date: Debuggin XNU build
  • Next by Date: Re: Debuggin XNU build
  • Previous by thread: Debuggin XNU build
  • Next by thread: Re: Debuggin XNU build
  • Index(es):
    • Date
    • Thread