Re: [Oorexx-devel] Segmentation fault in rexx executable

[Jason Martin]

r11811, OK it is still something.

Crash between run 8 and 9 still running

REMOVED THESE

rm  ooRexx/base/bif/ARG.testGroup
rm  ooRexx/base/bif/CHAROUT.testGroup
rm  ooRexx/base/bif/CONDITION.testGroup
rm  ooRexx/base/bif/LINEIN.testGroup
rm  ooRexx/base/bif/STREAM.testGroup
rm  ooRexx/base/class/Array.testGroup
rm  ooRexx/base/class/File.testGroup
rm  ooRexx/base/class/RexxContext.testGroup
rm  ooRexx/base/class/RexxQueue.testGroup
rm  ooRexx/base/class/Stream.testGroup
rm  ooRexx/base/keyword/ADDRESS.testGroup
rm  ooRexx/base/keyword/CALL.testGroup
rm  ooRexx/base/keyword/PARSE.testGroup
rm  ooRexx/base/keyword/SIGNAL.testGroup
rm  ooRexx/base/runtime.objects/environmentEntries.testGroup
rm  ooRexx/base/security.manager/SecurityManager.testGroup
rm  ooRexx/base/special.variables/RESULT_RC_SIGL.testGroup
rm  ooRexx/utilities/rexxc/rexxc.testGroup
rm  ooRexx/utilities/rxqueue/rxQueue.testGroup

START BASH SCRIPT

counter=0
while true; do
rexx testOORexx.rex -X native_api
counter=$((counter+1))
echo "Counter for rexx testOORexx.rex -X native_api : $counter
time(s); Sleeping for 10"
echo "Press [CTRL+C] to stop.."
sleep 10
done


ooTest Framework - Automated Test of the ooRexx Interpreter

Interpreter:REXX-ooRexx_5.0.0(MT)_64-bit 6.05 27 Feb 2019
OS Name:HAIKU
SysVersion: Haiku 1

Tests ran:  21252
Assertions: 339781
Failures:   0
Errors: 0

File search:00:00:01.728060
Suite construction: 00:00:01.865419
Test execution: 00:03:17.466434
Total time: 00:03:21.759626

Counter for rexx testOORexx.rex -X native_api : 8 time(s); Sleeping for 10
Press [CTRL+C] to stop..
Searching for test containers../count.sh: line 8:   826 Kill Thread
 rexx testOORexx.rex -X native_api
Counter for rexx testOORexx.rex -X native_api : 9 time(s); Sleeping for 10


___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Segmentation fault in rexx executable

[Rick McGuire]

All of those are identical and the variable values shown seriously don't
make sense. I just checked in a band-aid patch that should prevent this
from crashing. Perhaps this might cause some other failure to show up that
could give us some more information. None of the testGroups you identified
even do any of the things that would trigger that bit of code.

Rick

On Wed, Feb 27, 2019 at 1:32 PM Jason Martin  wrote:

> Added four more dump reports at
> https://github.com/agrellum/NetRexx-Samples
>
> All crashes are whatever ties these four groups.  They run one at a time
> fine.
>
> Array.testGroup
> CALL.testGroup
> RexxContext.testGroup
> SecurityManager.testGroup
>
> Finally get a batch run of 317 without these minus the 15 using shell
> commands.
>
>
> ___
> 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

Re: [Oorexx-devel] Segmentation fault in rexx executable

[Jason Martin]

Added four more dump reports at https://github.com/agrellum/NetRexx-Samples

All crashes are whatever ties these four groups.  They run one at a time fine.

Array.testGroup
CALL.testGroup
RexxContext.testGroup
SecurityManager.testGroup

Finally get a batch run of 317 without these minus the 15 using shell commands.


___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Segmentation fault in rexx executable

[Jason Martin]

This may help if someone can read these things.

https://github.com/agrellum/NetRexx-Samples/blob/master/rexx-645-debug-27-02-2019-11-25-43.report

https://github.com/agrellum/NetRexx-Samples/blob/master/rexx-742-debug-27-02-2019-11-29-19.report
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Segmentation fault in rexx executable

[Jason Martin]

I get it somtimes on OpenIndiana too.
I think on Haiku but have not got that far yet.
Never have got it on a single file.


___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Segmentation fault in rexx executable

[P.O. Jonsson]

Dear Enrico,

I am not trying to debug any particular part of ooRexx, everything runs just 
fine, all tests (including those I have written) pass without errors. What I am 
going after is a spurious problem:

REXX-ooRexx_5.0.0(MT)_64-bit 6.05 13 Feb 2019 r11755
Searching for test containers./Users/po/workspace/testooRexx.sh: line 37:  4122 
Segmentation fault: 11  rexx testOORexx.rex -s -X native_API

I have seen it happening on macOS and on Ubuntu, the segmentation fault just 
when rexx is starting. Running it again it runs just fine. It happens in 
average every 25-30 times I run the build (on Mac but also on Ubuntu)

Since I am not familiar with the debugger on Linux this was an excellent 
opportunity for me to learn about it.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se




> Am 27.02.2019 um 13:06 schrieb Enrico Sorichetti via Oorexx-devel 
> :
> 
> Dear P.O.
> 
> Running the test suite is not the best the way - IMO - to debug rexx
> The testSuite is sensitive to what is written to stdout and stderr 
> And it will usually report testSuite related non existent errors , 
> broken pipe, output mismatches, the most recurring ones
> And because of that it will nor run many sections of the test
> 
> Just isolate the section of the script being investigated 
> And run it outside of the test suite
> 
> Cheers 
> E
> 
> BTDTGTTS - been there  done that got the tee shirt
> 
> 
>> On 27 Feb 2019, at 12:40, P.O. Jonsson > > wrote:
>> 
>> Dear Moritz,
>> 
>> Sorry about the delay but I had pressing task and no time for ooRexx. Now I 
>> have tried to run the debugger (first-time-noob) but I do not understand the 
>> rexx core“ business, can you elaborate?
>> 
>> osboxes@osboxes:~/workspace/ooRexx-mint19-test$ ulimit -c 100
>> 
>> osboxes@osboxes:~/workspace/ooRexx-mint19-test$ gdb -silent rexx core
>> Reading symbols from rexx...done.
>> /home/osboxes/workspace/ooRexx-mint19-test/core: No such file or directory.
>> (gdb)
>> 
>> This works, at least to some extent
>> 
>> osboxes@osboxes:~/workspace/ooRexx-mint19-test$ gdb -silent -ex=r --args 
>> rexx testOORexx.rex -s -R ooRexx/samples
>> Reading symbols from rexx...done.
>> Starting program: /usr/bin/rexx testOORexx.rex -s -R ooRexx/samples
>> [Thread debugging using libthread_db enabled]
>> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
>> Searching for test containers[New Thread 0x77f56700 (LWP 7612)]
>> ..
>> Executing automated test suite
>> Executing .../ooRexx/samples/arithmeticEvaluation.testGroup
>> Executing .../ooRexx/samples/month.testGroup
>> 
>> ooTest Framework - Automated Test of the ooRexx Interpreter
>> 
>> Interpreter:REXX-ooRexx_5.0.0(MT)_64-bit 6.05 27 Feb 2019
>> OS Name:LINUX
>> SysVersion: Linux 4.15.0-45-generic
>> 
>> Tests ran:  11
>> Assertions: 90
>> Failures:   0
>> Errors: 0
>> 
>> File search:00:00:00.120060
>> Suite construction: 00:00:00.000917
>> Test execution: 00:00:00.256227
>> Total time: 00:00:00.760014
>> 
>> [Thread 0x77f56700 (LWP 7612) exited]
>> [Inferior 1 (process 7605) exited normally]
>> (gdb)
>> 
>> And in a real run (a shell script executing the test suite) I got some 
>> errors (that are not there when I run the suite outside the debugger)
>> 
>> osboxes@osboxes:~/workspace$ bash testooRexx.sh
>> + cd /home/osboxes/workspace/ooRexx-mint19-test
>> + svn update
>> Updating '.':
>> At revision 11810.
>> + . ./setTestEnv.sh
>> ++ UNAME_SYSTEM=Linux
>> ++ case "${UNAME_SYSTEM}" in
>> ++ echo 'Setting env for Linux'
>> Setting env for Linux
>> +++ pwd
>> +++ pwd
>> ++ 
>> frameworkPath=/home/osboxes/workspace/ooRexx-mint19-test:/home/osboxes/workspace/ooRexx-mint19-test/framework:
>> ++ export 
>> PATH=/home/osboxes/workspace/ooRexx-mint19-test:/home/osboxes/workspace/ooRexx-mint19-test/framework:/home/osboxes/workspace/ooRexx-mint19-test:/home/osboxes/workspace/ooRexx-mint19-test/framework:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
>> ++ 
>> PATH=/home/osboxes/workspace/ooRexx-mint19-test:/home/osboxes/workspace/ooRexx-mint19-test/framework:/home/osboxes/workspace/ooRexx-mint19-test:/home/osboxes/workspace/ooRexx-mint19-test/framework:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
>> +++ pwd
>> ++ export 
>> LD_LIBRARY_PATH=/home/osboxes/workspace/ooRexx-mint19-test/bin/LINUX:/home/osboxes/workspace/ooRexx-mint19-test/bin/LINUX:
>> ++ 
>> LD_LIBRARY_PATH=/home/osboxes/workspace/ooRexx-mint19-test/bin/LINUX:/home/osboxes/workspace/ooRexx-mint19-test/bin/LINUX:
>> + echo
>> 
>> + echo 
>> /home/osboxes/workspace/ooRexx-mint19-test:/home/osboxes/workspace/ooRexx-mint19-test/framework:/home/osboxes/workspace/ooRexx-mint19-test:/home/osboxes/workspace/ooRexx-mint19-test/framework:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
>> 

[Oorexx-devel] An example of taking advantage of the new variable reference feature

[Rony G. Flatscher]

While writing a little script to rewrite mailman mbox archive files to 
anonymize e-mail addresses,
the routine generating a pseudo-e-mail address would increase a counter each 
time.

While developing it a need popped up for a switch when invoking the script that 
allows one to
determine whether the counter should restart at 1 for every new mbox archive 
file or whether to use
a global counter starting at 1. This got realized with a Rexx class defining a 
class attribute
"counter" ("global counter") set to 1 in the class constructor (method 
"::method init class"), and
an instance attribute "counter" ("instance counter") set to 1 in the instance 
constructor (method
"::method init").

Using an array with two elements storing the variable references to the class 
and to the instance
attribute (changed each time a new instance gets created) I was able to solve 
this problem in a
quite easy manner: when invoking the routine that creates the pseudo-e-mail it 
will receive a
variable reference to the class or instance "counter" attribute depending on 
the switch. The routine
itself will only fetch the variable reference and increase the attribute 
counter directly without
without knowing whether it is actually the global or the instance counter!

Thought it might be interesting to see the new ooRexx 5.0 feature "variable 
reference" applied in a
real world scenario!

---rony

P.S.: BTW, the script uses the new ooRexx 5.0 ".context~package~local" 
environment to store the
supplied switch and the array with the variable references (as well as the 
current settings of all
possible options), making it easy to refer to all of them via their environment 
symbol (name of the
entry prepended with a dot '.') in the Rexx script.




___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Segmentation fault in rexx executable

[Enrico Sorichetti via Oorexx-devel]

Dear P.O.

Running the test suite is not the best the way - IMO - to debug rexx
The testSuite is sensitive to what is written to stdout and stderr 
And it will usually report testSuite related non existent errors , 
broken pipe, output mismatches, the most recurring ones
And because of that it will nor run many sections of the test

Just isolate the section of the script being investigated 
And run it outside of the test suite

Cheers 
E

BTDTGTTS - been there  done that got the tee shirt


> On 27 Feb 2019, at 12:40, P.O. Jonsson  wrote:
> 
> Dear Moritz,
> 
> Sorry about the delay but I had pressing task and no time for ooRexx. Now I 
> have tried to run the debugger (first-time-noob) but I do not understand the 
> rexx core“ business, can you elaborate?
> 
> osboxes@osboxes:~/workspace/ooRexx-mint19-test$ ulimit -c 100
> 
> osboxes@osboxes:~/workspace/ooRexx-mint19-test$ gdb -silent rexx core
> Reading symbols from rexx...done.
> /home/osboxes/workspace/ooRexx-mint19-test/core: No such file or directory.
> (gdb)
> 
> This works, at least to some extent
> 
> osboxes@osboxes:~/workspace/ooRexx-mint19-test$ gdb -silent -ex=r --args rexx 
> testOORexx.rex -s -R ooRexx/samples
> Reading symbols from rexx...done.
> Starting program: /usr/bin/rexx testOORexx.rex -s -R ooRexx/samples
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> Searching for test containers[New Thread 0x77f56700 (LWP 7612)]
> ..
> Executing automated test suite
> Executing .../ooRexx/samples/arithmeticEvaluation.testGroup
> Executing .../ooRexx/samples/month.testGroup
> 
> ooTest Framework - Automated Test of the ooRexx Interpreter
> 
> Interpreter:REXX-ooRexx_5.0.0(MT)_64-bit 6.05 27 Feb 2019
> OS Name:LINUX
> SysVersion: Linux 4.15.0-45-generic
> 
> Tests ran:  11
> Assertions: 90
> Failures:   0
> Errors: 0
> 
> File search:00:00:00.120060
> Suite construction: 00:00:00.000917
> Test execution: 00:00:00.256227
> Total time: 00:00:00.760014
> 
> [Thread 0x77f56700 (LWP 7612) exited]
> [Inferior 1 (process 7605) exited normally]
> (gdb)
> 
> And in a real run (a shell script executing the test suite) I got some errors 
> (that are not there when I run the suite outside the debugger)
> 
> osboxes@osboxes:~/workspace$ bash testooRexx.sh
> + cd /home/osboxes/workspace/ooRexx-mint19-test
> + svn update
> Updating '.':
> At revision 11810.
> + . ./setTestEnv.sh
> ++ UNAME_SYSTEM=Linux
> ++ case "${UNAME_SYSTEM}" in
> ++ echo 'Setting env for Linux'
> Setting env for Linux
> +++ pwd
> +++ pwd
> ++ 
> frameworkPath=/home/osboxes/workspace/ooRexx-mint19-test:/home/osboxes/workspace/ooRexx-mint19-test/framework:
> ++ export 
> PATH=/home/osboxes/workspace/ooRexx-mint19-test:/home/osboxes/workspace/ooRexx-mint19-test/framework:/home/osboxes/workspace/ooRexx-mint19-test:/home/osboxes/workspace/ooRexx-mint19-test/framework:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
> ++ 
> PATH=/home/osboxes/workspace/ooRexx-mint19-test:/home/osboxes/workspace/ooRexx-mint19-test/framework:/home/osboxes/workspace/ooRexx-mint19-test:/home/osboxes/workspace/ooRexx-mint19-test/framework:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
> +++ pwd
> ++ export 
> LD_LIBRARY_PATH=/home/osboxes/workspace/ooRexx-mint19-test/bin/LINUX:/home/osboxes/workspace/ooRexx-mint19-test/bin/LINUX:
> ++ 
> LD_LIBRARY_PATH=/home/osboxes/workspace/ooRexx-mint19-test/bin/LINUX:/home/osboxes/workspace/ooRexx-mint19-test/bin/LINUX:
> + echo
> 
> + echo 
> /home/osboxes/workspace/ooRexx-mint19-test:/home/osboxes/workspace/ooRexx-mint19-test/framework:/home/osboxes/workspace/ooRexx-mint19-test:/home/osboxes/workspace/ooRexx-mint19-test/framework:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
> /home/osboxes/workspace/ooRexx-mint19-test:/home/osboxes/workspace/ooRexx-mint19-test/framework:/home/osboxes/workspace/ooRexx-mint19-test:/home/osboxes/workspace/ooRexx-mint19-test/framework:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
> + echo
> 
> + echo 
> /home/osboxes/workspace/ooRexx-mint19-test/bin/LINUX:/home/osboxes/workspace/ooRexx-mint19-test/bin/LINUX:
> /home/osboxes/workspace/ooRexx-mint19-test/bin/LINUX:/home/osboxes/workspace/ooRexx-mint19-test/bin/LINUX:
> + echo
> 
> + rexx -e 'parse version v; say v '\''r'\'' || .RexxInfo~revision'
> REXX-ooRexx_5.0.0(MT)_64-bit 6.05 27 Feb 2019 r11810
> + sleep 1
> + ulimit -c 100
> + gdb -silent -ex=r --args rexx testOORexx.rex -s -X native_API
> Reading symbols from rexx...done.
> Starting program: /usr/bin/rexx testOORexx.rex -s -X native_API
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> Searching for test containers[New Thread 

Re: [Oorexx-devel] Segmentation fault in rexx executable

[P.O. Jonsson]

Dear Moritz,

Sorry about the delay but I had pressing task and no time for ooRexx. Now I 
have tried to run the debugger (first-time-noob) but I do not understand the 
rexx core“ business, can you elaborate?

osboxes@osboxes:~/workspace/ooRexx-mint19-test$ ulimit -c 100

osboxes@osboxes:~/workspace/ooRexx-mint19-test$ gdb -silent rexx core
Reading symbols from rexx...done.
/home/osboxes/workspace/ooRexx-mint19-test/core: No such file or directory.
(gdb)

This works, at least to some extent

osboxes@osboxes:~/workspace/ooRexx-mint19-test$ gdb -silent -ex=r --args rexx 
testOORexx.rex -s -R ooRexx/samples
Reading symbols from rexx...done.
Starting program: /usr/bin/rexx testOORexx.rex -s -R ooRexx/samples
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Searching for test containers[New Thread 0x77f56700 (LWP 7612)]
..
Executing automated test suite
Executing .../ooRexx/samples/arithmeticEvaluation.testGroup
Executing .../ooRexx/samples/month.testGroup

ooTest Framework - Automated Test of the ooRexx Interpreter

Interpreter:REXX-ooRexx_5.0.0(MT)_64-bit 6.05 27 Feb 2019
OS Name:LINUX
SysVersion: Linux 4.15.0-45-generic

Tests ran:  11
Assertions: 90
Failures:   0
Errors: 0

File search:00:00:00.120060
Suite construction: 00:00:00.000917
Test execution: 00:00:00.256227
Total time: 00:00:00.760014

[Thread 0x77f56700 (LWP 7612) exited]
[Inferior 1 (process 7605) exited normally]
(gdb)

And in a real run (a shell script executing the test suite) I got some errors 
(that are not there when I run the suite outside the debugger)

osboxes@osboxes:~/workspace$ bash testooRexx.sh
+ cd /home/osboxes/workspace/ooRexx-mint19-test
+ svn update
Updating '.':
At revision 11810.
+ . ./setTestEnv.sh
++ UNAME_SYSTEM=Linux
++ case "${UNAME_SYSTEM}" in
++ echo 'Setting env for Linux'
Setting env for Linux
+++ pwd
+++ pwd
++ 
frameworkPath=/home/osboxes/workspace/ooRexx-mint19-test:/home/osboxes/workspace/ooRexx-mint19-test/framework:
++ export 
PATH=/home/osboxes/workspace/ooRexx-mint19-test:/home/osboxes/workspace/ooRexx-mint19-test/framework:/home/osboxes/workspace/ooRexx-mint19-test:/home/osboxes/workspace/ooRexx-mint19-test/framework:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
++ 
PATH=/home/osboxes/workspace/ooRexx-mint19-test:/home/osboxes/workspace/ooRexx-mint19-test/framework:/home/osboxes/workspace/ooRexx-mint19-test:/home/osboxes/workspace/ooRexx-mint19-test/framework:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
+++ pwd
++ export 
LD_LIBRARY_PATH=/home/osboxes/workspace/ooRexx-mint19-test/bin/LINUX:/home/osboxes/workspace/ooRexx-mint19-test/bin/LINUX:
++ 
LD_LIBRARY_PATH=/home/osboxes/workspace/ooRexx-mint19-test/bin/LINUX:/home/osboxes/workspace/ooRexx-mint19-test/bin/LINUX:
+ echo

+ echo 
/home/osboxes/workspace/ooRexx-mint19-test:/home/osboxes/workspace/ooRexx-mint19-test/framework:/home/osboxes/workspace/ooRexx-mint19-test:/home/osboxes/workspace/ooRexx-mint19-test/framework:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
/home/osboxes/workspace/ooRexx-mint19-test:/home/osboxes/workspace/ooRexx-mint19-test/framework:/home/osboxes/workspace/ooRexx-mint19-test:/home/osboxes/workspace/ooRexx-mint19-test/framework:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
+ echo

+ echo 
/home/osboxes/workspace/ooRexx-mint19-test/bin/LINUX:/home/osboxes/workspace/ooRexx-mint19-test/bin/LINUX:
/home/osboxes/workspace/ooRexx-mint19-test/bin/LINUX:/home/osboxes/workspace/ooRexx-mint19-test/bin/LINUX:
+ echo

+ rexx -e 'parse version v; say v '\''r'\'' || .RexxInfo~revision'
REXX-ooRexx_5.0.0(MT)_64-bit 6.05 27 Feb 2019 r11810
+ sleep 1
+ ulimit -c 100
+ gdb -silent -ex=r --args rexx testOORexx.rex -s -X native_API
Reading symbols from rexx...done.
Starting program: /usr/bin/rexx testOORexx.rex -s -X native_API
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Searching for test containers[New Thread 0x77f56700 (LWP 8018)]
[New Thread 0x77ed5700 (LWP 8019)]
...
Executing automated test suite
Executing .../ooRexx/SimpleTests.testGroup
Executing .../ooRexx/base/bif/ABBREV.testGroup
Executing .../ooRexx/base/bif/ABS.testGroup
Executing .../ooRexx/base/bif/ADDRESS.testGroup
Executing .../ooRexx/base/bif/ARG.testGroup
Executing .../ooRexx/base/bif/B2X.testGroup
Executing .../ooRexx/base/bif/BEEP.testGroup
Executing .../ooRexx/base/bif/BITAND.testGroup
Executing .../ooRexx/base/bif/BITOR.testGroup
Executing .../ooRexx/base/bif/BITXOR.testGroup
Executing .../ooRexx/base/bif/C2D.testGroup
Executing .../ooRexx/base/bif/C2X.testGroup
Executing .../ooRexx/base/bif/CENTER.testGroup
Executing .../ooRexx/base/bif/CENTRE.testGroup