How were you able to determine that the syssleep call was the stopping point? Are you able to get stack traces for any other threads? I can think of two possible reasons for freezing there: 1) a bug in whatever the *ix version of syssleep is using to sleep, or 2) there is an error in thread dispatch and/or the semaphores that is causing a deadlock when the syssleep function attempts to return to the interpreter. If you can determine the place in the code where syssleep is stuck, I might be able to eliminate one of these possibilities....and I'm praying option 2) is the one eliminated.
Rick On Wed, Jul 1, 2009 at 11:53 AM, David Ashley<david.ashley....@gmail.com> wrote: > All - > > I built the s390x rpm from the rc1 source tar file. While it seems to > work fine the test suite never finishes, it runs forever. I manually > killed it and then checked rxapi, it was still running. The stopping > point was a syssleep instruction in the framework. > > Any ideas? > > David Ashley > > ------------------------------------------------------------------------------ > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > ------------------------------------------------------------------------------ _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
