Re: [Oorexx-devel] Question on Halt() and possibility of interfering with Java's signal handling?

2009-06-05 Thread Rony G. Flatscher
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

[Oorexx-devel] Question on Halt() and possibility of interfering with Java's signal handling?

2009-06-04 Thread Rony G. Flatscher
Having proceeded to a point in which I am confident that dispatching Rexx intepreter instances on separate Java threads is stable, I turned back to a use case from a BSF4Rexx user who tries to halt Rexx threads from Java. In the 4.0 API version the Halt() API of the interpreter instance is used

Re: [Oorexx-devel] Question on Halt() and possibility of interfering with Java's signal handling?

2009-06-04 Thread Rick McGuire
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

Re: [Oorexx-devel] Question on Halt() and possibility of interfering with Java's signal handling?

2009-06-04 Thread Rony G. Flatscher
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's

Re: [Oorexx-devel] Question on Halt() and possibility of interfering with Java's signal handling?

2009-06-04 Thread Rick McGuire
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 rony.flatsc...@wu-wien.ac.at wrote: