|
From: Tom H. <th...@cy...> - 2004-09-13 06:10:23
|
In message <200...@ac...>
Julian Seward <js...@ac...> wrote:
> I'm not clear what the root cause of the problem was (which
> set of changes yesterday caused it?) and in particular
> whether the fix needs to be done also on _2_2_0_BRANCH ?
It was the stack limit enforcing. Because stack_size in the thread
state for the main thread was changed so that it recorded the maximum
possible size rather than the initial size it meant that when the main
thread was killed at the end it called die_mem_stack on stack_size bytes
and if there was no limit that was a very large number.
I changed it to lookup the segment containing the stack and only call
die_mem_stack on the portion of the stack that had actually been used.
I don't think that change is on the 2.2.0 branch.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|