From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kip Macy 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 Message-ID: References: Reply-To: Kip Macy Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com, Kip Macy List-Id: xen-devel@lists.xenproject.org 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 wrote: >=20 > > 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. >=20 > 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. >=20 > -- Keir >=20 >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >