Hello,
I just have rebuild the beta. Unfortunately the testsuite hangs...
AIX / 32 bit build / SVN 4688:
60 *-* expose called
42 *-* trap = .PullTrap~new
REX0048E: Error 48 running
/daten/source/ooRexx/test/trunk/ooRexx/API/oo/tests/traceExit.rex line
60: Failure in syste
REX0425E:
Make sure that you've got the correct version of rxapi running. There
was also one change to the APIs, so make sure you've rebuilt all of
the programs used for the external tests.
Rick
On Sun, May 17, 2009 at 5:07 AM, Rainer Tammer tam...@tammer.net wrote:
Hello,
I just have rebuild the beta.
Hello,
Rick McGuire wrote:
Make sure that you've got the correct version of rxapi running.
I kill the rxapi 3 times, cleaned the shared memory and reinstalled rexx
... no luck.
The standard samples are working
There
was also one change to the APIs, so make sure you've rebuilt all of
On Sun, May 17, 2009 at 4:20 AM, Rick McGuire object.r...@gmail.com wrote:
Make sure that you've got the correct version of rxapi running. There
was also one change to the APIs, so make sure you've rebuilt all of
the programs used for the external tests.
Rainer,
If you use the -B option it
On Sun, May 17, 2009 at 7:56 AM, Rainer Tammer tam...@tammer.net wrote:
Rick McGuire wrote:
Make sure that you've got the correct version of rxapi running.
I kill the rxapi 3 times, cleaned the shared memory and reinstalled rexx
... no luck.
Rainer,
If I had something like this on a Linux
Rick,
When I run the test suite on Fedora Core 10 32-bit, I get a
segmentation fault. (4691)
I've just built and tested the 64-bit version on both Fedora Core 10
and Kubuntu and the test suite ran on both of them without a problem.
I've got a bunch of family commitments right now and everyone
Mark,
I'm not getting too far on this. I had to comment out the different
many_chars tests in CHAROUT.TestGroup. Trying to manipulate 200Mb
objects in a virtual machine that is only configured with 256Mb of
memory causes some serious memory thrashing. Once I got past that, it
seems to have
On Sun, May 17, 2009 at 3:45 PM, Rick McGuire object.r...@gmail.com wrote:
I'm not getting too far on this. I had to comment out the different
many_chars tests in CHAROUT.TestGroup. Trying to manipulate 200Mb
objects in a virtual machine that is only configured with 256Mb of
memory causes
When raising a condition via native code, is it possible to supply an
(additional) object with the condition to be raised, such that one is
able to fetch it from a condition object?
The intent is to supply a Java Throwable object with a Rexx condition
that gets raised as a result of a thrown Java
Rick,
Not sure if this helps much when taken with the stack trace I sent
you, but the test case that causes the seg fault is:
::method test_queryDir_not_exists
In ooRexx/base/bif/STREAM.testGroup
--
Mark Miesfeld
On Sun, May 17, 2009 at 3:45 PM, Rick McGuire object.r...@gmail.com wrote:
If you are raising a condition (not a SYNTAX error), that is the
additional argument for RaiseCondition(). For SYNTAX errors, no. The
Additional information is always the error message substitution
values.
Rick
On Sun, May 17, 2009 at 7:52 PM, Rony G. Flatscher
rony.flatsc...@wu-wien.ac.at
11 matches
Mail list logo
