On Wed, Nov 14, 2007 at 11:35:56AM +0100, Miklos Szeredi wrote:
> Note, this is 32bit UML on 64bit host, to complicate matters. So I
> think it's not PTRACE_ARCH_PRCTL, but PTRACE_SET_THREAD_AREA.
Oh, that changes things. In this case, I believe this problem is fixed
by fd181c72a3c202a3986bcee7551c0838265aec2a.
You'll also need f86f9e6d66027bdcdc9b40c06d431ee53ea0d509 for a
separate problem.
> Maybe this is a fallout from the x86 architecture merge?
No, the problems had been there from before the merge - years, in the
case of the second one.
Jeff
--
Work email - jdike at linux dot intel dot com
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
