[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v2] x86/emul: Poision the stubs with debug traps
>>> On 30.03.17 at 19:09, <andrew.cooper3@xxxxxxxxxx> wrote: > If you do have an external debugger attached, you don't need embedded > int3's to start with, and you'd still hit the debugger_trap_*() calls > before dying. Well, my experience (on other OSes with a better debugger) is different - there are occasions where it is easier to embed an int3 right away than to break into the system (doing of which may be a problem of its own if you need the breakpoint quite early during boot), go hunt for the precise instruction you want the breakpoint on, and then set the intended breakpoint using debugger facilities. > If you don't have an external debugger attached, ignoring int3's is very > poor behaviour. Well, that's your opinion. Mine (again based on past experience) is different, and it appears to match that of whoever originally wrote things this way. Nevertheless I appreciate the (assumed) reasoning behind your way of thinking. Jan _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx https://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |