From: Kip Macy <kip.macy@gmail.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, Kip Macy <kmacy@netapp.com>
Subject: Re: Re: possible changes was Re: [PATCH] make domu_debug run-time option + fix int3 handling for MP
Date: Mon, 16 May 2005 13:33:50 -0700 [thread overview]
Message-ID: <b1fa291705051613331d87ee7f@mail.gmail.com> (raw)
In-Reply-To: <e354ab81554c8192bffce5d2b9214c2c@cl.cam.ac.uk>
I guess I don't see how this is any different from the per-process
ptrace flag on UN*X. Why is this any more of a kludge?
-Kip
On 5/16/05, Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote:
>
> > No differentiation is made between setting / removing int3 and other
> > modifications to memory in ptrace, /proc or the GDB stub protocol.
> > What you're
> > basically asking is to move debugger state into xen by having xen know
> > about who
> > put what breakpoints where. This is a non-trivial imposition and
> > incompatible
> > with the tools with which I am acquainted.
>
> How else can we be sure what to do with int3 traps? Unless Xen can
> account for debugger-inserted int3's, any 'solution' will be a kludge.
>
> -- Keir
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2005-05-16 20:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-16 1:25 [PATCH] make domu_debug run-time option + fix int3 handling for MP Kip Macy
2005-05-16 19:07 ` possible changes was " Kip Macy
2005-05-16 20:10 ` Keir Fraser
2005-05-16 20:26 ` Kip Macy
2005-05-16 20:28 ` Keir Fraser
2005-05-16 20:33 ` Kip Macy [this message]
2005-05-16 20:40 ` Keir Fraser
2005-05-16 20:46 ` Kip Macy
2005-05-16 21:55 ` Christian Limpach
2005-05-16 22:08 ` Kip Macy
2005-05-16 22:18 ` Christian Limpach
2005-05-16 22:23 ` 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=b1fa291705051613331d87ee7f@mail.gmail.com \
--to=kip.macy@gmail.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=kmacy@netapp.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.