On Fri, Apr 13, 2007 at 09:31:16AM -0700, Haifeng He wrote:
> Yes. So that is the problem. Is there any other place which may cause
> similar problems?
If you're going to be sprinking code randomly around UML, you need to
be cognizant of what stack the surrounding code runs on.
You hit code which
On 4/13/07, Jeff Dike <[EMAIL PROTECTED]> wrote:
On Thu, Apr 12, 2007 at 10:14:32PM -0700, Haifeng He wrote:
> 3. foo is called at many places.
>
> If not, what could be the cause for such error? The strange thing is,
> if I just read value of "a" from "current", kernel runs fine.
Did you put a
On Thu, Apr 12, 2007 at 10:14:32PM -0700, Haifeng He wrote:
> 3. foo is called at many places.
>
> If not, what could be the cause for such error? The strange thing is,
> if I just read value of "a" from "current", kernel runs fine.
Did you put a call in userspace_tramp?
Hi,
I met a program error when I tried to modify UML kernel. What I did was:
1. added a variable "a" in struct task_struct.
2. I wrote a function that will update the value of "a" in task struct
"current", i.e.,
something like:
foo () {
current->a = xx.
}
3. foo is called at many places.
