 Home |
Products |
Support |
Community |
News |
xen-devel
Re: [Xen-devel] Re: possible changes was Re: [PATCH] make domu_debug run
| To: | Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [Xen-devel] Re: possible changes was Re: [PATCH] make domu_debug run-time option + fix int3 handling for MP |
| From: | Kip Macy <kip.macy@xxxxxxxxx> |
| Date: | Mon, 16 May 2005 13:33:50 -0700 |
| Cc: | xen-devel@xxxxxxxxxxxxxxxxxxx, Kip Macy <kmacy@xxxxxxxxxx> |
| Delivery-date: | Mon, 16 May 2005 20:33:20 +0000 |
| Domainkey-signature: | a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=pGg5g3r+BNsqp0H+as6Pe6+/0ZOfZagd9+bPLE9YBEH4Xnoh2sO1ISDtWhnMHFX+uVyPXHzxAdbELZth9RKj+2ZfgDyQ24NtrgWZID0m2IRGjmuCOO9Uk8qovRE3MthdmB60hLOZ7v0t+j0ItUMPexisI4OQ9hqS52SMkSADYT8= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| In-reply-to: | <e354ab81554c8192bffce5d2b9214c2c@xxxxxxxxxxxx> |
| List-help: | <mailto:xen-devel-request@lists.xensource.com?subject=help> |
| List-id: | Xen developer discussion <xen-devel.lists.xensource.com> |
| List-post: | <mailto:xen-devel@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| References: | <Pine.LNX.4.44.0505161318070.16537-100000@xxxxxxxxxxxxxxxxxxxxxx> <e354ab81554c8192bffce5d2b9214c2c@xxxxxxxxxxxx> |
| Reply-to: | Kip Macy <kip.macy@xxxxxxxxx> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
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@xxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
| Previous by Date: | RE: [Xen-devel] possible changes was Re: [PATCH] make domu_debug run-time option + fix int3 handling for MP, Ian Pratt |
|---|---|
| Next by Date: | Re: FW: [Xen-devel] Creating domain crashes xend with the latest xenunstable tree, Mike Wray |
| Previous by Thread: | [Xen-devel] Re: possible changes was Re: [PATCH] make domu_debug run-time option + fix int3 handling for MP, Keir Fraser |
| Next by Thread: | Re: [Xen-devel] Re: possible changes was Re: [PATCH] make domu_debug run-time option + fix int3 handling for MP, Keir Fraser |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
