All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Neo Jia <neojia@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: debugger updates...
Date: Fri, 07 Nov 2008 10:52:04 -0800	[thread overview]
Message-ID: <49148E54.5010705@oracle.com> (raw)
In-Reply-To: <5d649bdb0811062226p3f5ed1bbtdf76a9b54578ed57@mail.gmail.com>

kdb is intended to debug xen hypervisor... can be used for dom0 also.
gdbsx is intended to debug domU (PV or HVM).

Thanks,
Mukesh

Neo Jia wrote:
> Can I use this to debug Xen or it is just for dom0?
> 
> Thanks,
> Neo
> 
> On Thu, Nov 6, 2008 at 6:58 PM, Mukesh Rathor <mukesh.rathor@oracle.com> wrote:
>> Hi all,
>>
>> FYI... I've updated the debuggers (kdb + gdbsx) tree.  Here's a summary:
>>
>>  - Refresh to changeset 18711
>>
>>  - gdbsx: Add support for HVM guest debug.
>>           Support for kernel module debug in PV linux guests (via pgd3val)
>>           Include gdb macros (in README) for linux kernel/module debug
>>
>>  - kdb: HVM guest debug support (set bp, single step)
>>         Display VMCB/VMCS structs, more structs, etc.
>>         Generic Trace function: to quickly debug something, esp, timing
>>                                 related problems
>>         General kdb trap func: kdb_trap_immed() to break into kdb anywhere,
>>                                possibly based on a condition.....
>>
>> See READMEs in http://xenbits.xensource.com/ext/debuggers.hg
>>
>> Thanks,
>> Mukesh
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>
> 
> 
> 

  reply	other threads:[~2008-11-07 18:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-07  2:58 debugger updates Mukesh Rathor
2008-11-07  6:26 ` Neo Jia
2008-11-07 18:52   ` Mukesh Rathor [this message]
2008-11-07 18:54     ` Neo Jia

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49148E54.5010705@oracle.com \
    --to=mukesh.rathor@oracle.com \
    --cc=neojia@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.