Bob Jewett

Request MutexSemaphore Class with a name option

Sorry about the Anonymous message yesterday. I have been able to create an ooRexx "test_thread" program that shows the segfault on my Debian 10 (Buster) 64bit system. Because it fails so infrequently, I have also created a bash script "test_loop" to run it. Attached are the 2 programs and a "test_thread_msg" file containing the results of the "test_loop" bash script. Please let me know if this works.

Erich, The revision I am using is r12143. I'm not sure that I understand what you are looking for. I captured r12143 using svn to a local directory and compiled both debug and non debug ooRexx from it. I have not updated it since. The segfault is very intermittent. I do not have any sample code that shows the problem. I am currently running the ooRexx debug version on my system. One program (dispatched using linux cron every 5 minutes) starts a concurrent thread to test devices on my LAN (one device...

Ok, I decided to remove the current ooRexx package and install ooRexx from a DEBUG deb package I compiled from a local oorexxsvn directory containing r12143. I have an oorexx program running as a daemon named evolution-sync. I just realized that this program is crashing quite frequently. It has been getting crashes and other errors since I installed r12142. I had an older 5.0.0 revision (maybe r11969) installed before this and it was not having a problem. So I have attached a file containing a stack...

Sorry about the Anonymous post above. I have downloaded the source from svn and compiled both RELEASE and DEBUG versions. I have installed the executables in there own respective private folders not included in the PATH environment. I have created a couple of scripts, one for RELEASE and one for DEBUG. They temporary change the paths before invoking the rexx application to start a passed ooRexx program . This seems to override the shebang on the first line of the ooRexx program. I have several ooRexx...

Intermittent Segfaults

It just seemed to me that parsing all of them in one line like a PARSE CARG or USE CARG simplifies the code, especially when one or more arguments passed are double quoted.

This does not appear to be a bug so it should be rejected.