All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kip Macy <kip.macy@gmail.com>
To: jfv@bluesong.net
Cc: 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:05:30 -0800	[thread overview]
Message-ID: <b1fa2917050312110515eb233d@mail.gmail.com> (raw)
In-Reply-To: <20050312185848.GA16403@trane.bluesong.net>

> I
> > > think
> > > this needs some kind of flag to enable/disable this behaviour.
> >
> > I thought about that, but is there an In-guest kernel debugger that
> > can set breakpoints? All I know of are stubs that require a serial
> > port. Does NetBSD's in-kernel debugger allow one to set breakpoints
> > and continue? If so I can just put the debugger option back in
> > Rules.mk.

I spoke / wrote too soon. DDB probably does this as well. Although
I've never used it. I'd be surprised if most people didn't find the
user-level gdbserver more useful and generic than in-kernel debuggers.

Rather than being a compile-time option it should be a boot-time option.

> I believe there is a kdb patch for i386 Linux, and I have intended
> to extend my x86_64 kdb patch to Xen soon.

Cool.

> 
> 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?

Interesting. In the meantime, unless someone beats me to it (wishful
thinking), I'll be extending cdb into a normal stop and continue GDB
stub.

> 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 :)

That sounds more like what I've implemented than an in-kernel solution.

               -Kip


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

  parent reply	other threads:[~2005-03-12 19:05 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
2005-03-12 19:05     ` Kip Macy [this message]
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=b1fa2917050312110515eb233d@mail.gmail.com \
    --to=kip.macy@gmail.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=jfv@bluesong.net \
    --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.