Just wanted to report that the problem has gone away and it had nothing
to do with ooRexx or Java, but with a coding error: in the code path
there was a condition which caused the invocation of RexxFreeMemory() on
the same pointer twice. This obviously caused the observed behaviour
that I reported
I did spot a resource locking problem in the Halt() API that could
create a race condition that might result in a memory overlay. I've
fixed that, but there really is not much else involved with that API.
Rick
On Thu, Jun 4, 2009 at 5:34 PM, Rony G. Flatscher
wrote:
>
> Rick McGuire wrote:
>> H
Rick McGuire wrote:
> Halt() does not use any signalling mechanisms. It only iterates
> through the threads associated with each instance and sets a flag
> indicating that a halt condition needs to be raised. That flag is
> detected at instruction boundaries and the condition gets raised.
> That
Halt() does not use any signalling mechanisms. It only iterates
through the threads associated with each instance and sets a flag
indicating that a halt condition needs to be raised. That flag is
detected at instruction boundaries and the condition gets raised.
That's all that this does.
Rick
O
