Re: [Oorexx-devel] Problem with SysStemSort, but ...

2009-05-26 Thread Rony G. Flatscher
Rick McGuire wrote: I just thought of one more thing that could cause the error you're seeing. If you do an AttachThread() at some point and neglect to do a corresponding DetachThread() before returning to your caller, you'll end up with a corrupted activaation stack that will result in

Re: [Oorexx-devel] Problem with SysStemSort, but ...

2009-05-26 Thread Rony G. Flatscher
Rick McGuire wrote: This is exactly the last scenario I described to you yesterday and you adamantly declared that RexxCreateInterpreter was not getting called. There is an association between a thread and the top-most thread context that is created on that thread. Once you call

Re: [Oorexx-devel] Problem with SysStemSort, but ...

2009-05-26 Thread Rick McGuire
Note that you really have very limited ability to do anything in a package unloader. At this point, everything is shutting down. All of the instances have been cleaned up already and this is one of the very last steps in the process of cleaning thiings up. I doesn't surprise me that you might

Re: [Oorexx-devel] Problem with SysStemSort, but ...

2009-05-25 Thread Rony G. Flatscher
Rick McGuire wrote: I just thought of one more thing that could cause the error you're seeing. If you do an AttachThread() at some point and neglect to do a corresponding DetachThread() before returning to your caller, you'll end up with a corrupted activaation stack that will result in

[Oorexx-devel] Problem with SysStemSort, but ...

2009-05-24 Thread Rony G. Flatscher
Got an exception with applying SysStemSort(), the debugger pointing to RexxLocalVariables.hpp, inline function: inline RexxVariable *get(size_t index) { return locals[index]; } with index=0. Unfortunately, I am not able to create an isolated test case. If I write the stem's values into a

Re: [Oorexx-devel] Problem with SysStemSort, but ...

2009-05-24 Thread Rick McGuire
Definitely not enough to determine the problem. This very much looks like there had to have been an memory overlay based on the location of the trap. The most likely explanation is a wild store by some other external routine, perhaps a problem in BSFRexx itself. Rick On Sun, May 24, 2009 at

Re: [Oorexx-devel] Problem with SysStemSort, but ...

2009-05-24 Thread Rick McGuire
Rony, I just thought of one more thing that could cause the error you're seeing. If you do an AttachThread() at some point and neglect to do a corresponding DetachThread() before returning to your caller, you'll end up with a corrupted activaation stack that will result in problems with legacy