|
From: Tom H. <to...@co...> - 2005-03-04 15:43:52
|
In message <200...@ac...>
Julian Seward <js...@ac...> wrote:
>> So I'd suggest implementing the client request as Jeremy says, and then
>> tweaking the heuristic so that the %esp-delta has to be substantially
>> bigger (say, 8MB) before Memcheck assumes it's a stack-switch. And add a
>> FAQ about it.
>
> Yes, I agree. But (1) not for 2.4.0, and (2) how does this client
> request work? The client request needs to happen atomically with
> the new assignment to the stack pointer; I don't see how that can
> happen.
I thought Jeremy's suggestion was to have a request that would
declare an area of memory as a stack so that valgrind would know
that when the stack pointer moved from one "stack area" to another
one then it would know it was a stack switch.
Obviously valgrind would have to mark the areas used by cloned
threads as stacks, as well as the initial stack.
I have no idea if that is all workable, but it is what I though
had been suggested anyway and it doesn't seem to require an atomic
request and update stack pointer operation.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|