From: Wim Coekaerts <wim.coekaerts@oracle.com>
To: Jack F Vogel <jfv@bluesong.net>
Cc: Kip Macy <kip.macy@gmail.com>,
Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
xen-devel@lists.sourceforge.net,
Keir Fraser <Keir.Fraser@cl.cam.ac.uk>Ian.Pratt@cl.cam.ac.uk,
Christian Limpach <Christian.Limpach@cl.cam.ac.uk>,
jfv@us.ibm.com
Subject: Re: Re: follow-up to guest debug support patches
Date: Sat, 12 Mar 2005 11:04:27 -0800 [thread overview]
Message-ID: <20050312190426.GC24578@ca-server1.us.oracle.com> (raw)
In-Reply-To: <20050312185848.GA16403@trane.bluesong.net>
> I had even had thoughts of an extended debugger in dom0, but have
> been too busy to think that through. Any thoughts from others on
> that? I recall a particularly nasty AIX bug that I worked on once
> on an S390 machine, the debugger in the nucleus (on VM/ESA) allowed
> me to set a watchpoint outside the guest and made a memory corruption
> problem MUCH easier to track down :)
this is one of the main interests I have - would make things in
production servers so much easier to debug .
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-12 19:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-12 16:02 follow-up to guest debug support patches Ian Pratt
2005-03-12 17:13 ` Keir Fraser
2005-03-12 18:40 ` Kip Macy
2005-03-12 18:58 ` Jack F Vogel
2005-03-12 19:04 ` Wim Coekaerts [this message]
2005-03-12 19:05 ` Kip Macy
2005-03-12 20:27 ` Christian Limpach
2005-03-12 19:46 ` Christian Limpach
2005-03-12 20:06 ` Kip Macy
2005-03-12 21:22 ` New patch was " Kip Macy
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=20050312190426.GC24578@ca-server1.us.oracle.com \
--to=wim.coekaerts@oracle.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=jfv@bluesong.net \
--cc=kip.macy@gmail.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/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.