Messages in this thread | | | From | Alexandre Julliard <> | Subject | Re: Regression in ptrace (Wine) starting with 2.6.33-rc1 | Date | Mon, 15 Feb 2010 16:57:08 +0100 |
| |
"K.Prasad" <prasad@linux.vnet.ibm.com> writes:
> We could change this to become 'local' for every local request (but still > cleanup the breakpoints using scheduler hooks like the way we presently > do), but I think this is an implementation detail and that a ptrace user > need not worry about it. Or do you believe that there's any? > > I'm afraid I don't understand your motivation for these read/write tests > on debug control register? Such tests, as in this case, cause unnecessary > panic due to changes in an implementation detail internal to the kernel > without any perceptible difference in functionality.
Various copy protection schemes such as Safedisc do all sorts of strange manipulations and checks on the debug registers, in an attempt to make sure that the app is not being run under a debugger. The Wine exception tests try to replicate that behavior.
-- Alexandre Julliard julliard@winehq.org
| |