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 (much later though).
Once found and fixed, everything now works in this area as it should. ---rony Rick McGuire wrote: > 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: > >> 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 all that this does. >>> >>> >> Thanks, that really helps a lot, because then I will concentrate to look >> over the code thoroughly to see what might cause this. >> >> ---rony >> ------------------------------------------------------------------------------ OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
