From: Mark M. <mmi...@am...> - 2007-01-24 22:12:39
|
Rony, =20 Red Hat FC3: running the testUnits ("rexxTestUnits -r .") will cause a Segmentation fault. This can also be evoked by running the testUnit "./ooRexx.Base.BIF.testUnit".=20 Shall I file a bug report for this? =20 No, not if you are using the 3.1.1 release. This is surely the bug that is fixed in cvs, the same bug Michael reported. (E-mail me off line if you want me to build you a rpm with the fix incorporated to make sure.) =20 -- Mark Miesfeld mmi...@am...=20 =20 ________________________________ From: oor...@li... [mailto:oor...@li...] On Behalf Of Rony G. Flatscher Sent: Wednesday, January 24, 2007 2:02 PM To: Open Object Rexx Developer Mailing List Subject: [Oorexx-devel] New ooRexxUnit drop: two problems ... Hi there, as you might have seen, there is a refresh of the ooRexxUnit framework available via CVS.=20 There have been two changes: * all CR-LF sequences have been replaced by LF. This is to cater for correct Unix-hash-bang processing (leaving the CR would cause an error),=20 * there is a new public routine "ooRexxUnit.getShellName()" which returns the (guessed) shell name one should ADDRESS; this is meant for a central location for determining the shell name and should allow easying maintenance.=20 Running the testUnits under: * Windows looks o.k.,=20 * Ubuntu 6.10 looks o.k., except that there is one failure (which also occurs on RedHat FC3):=20 [20070124 22:29:32.806157]: [failure] testCase: [TEST_RESULT_WITH_EXIT_ADDRESSING_EXTERNALFILE] (an ooRexx.Base.RESULT_RC_SIGL.testUnit@7420E82D) ---> @assertFailure assertSame: expected=3D[[1234], hashValue=3D"69323334"x], = actual=3D[[210], hashValue=3D"65310000"x]. subTest3 =09 so the testUnit file "ooRexx.Base.RESULT_RC_SIGL.testUnit" contains a test case method "TEST_RESULT_WITH_EXIT_ADDRESSING_EXTERNALFILE" in which the assertion named "subTest3" fails: the test causes an external Rexx program to be invoked with a separate instance of the Rexx interpreter and it should return the return code "1234" (set via an EXIT statement in the executed external Rexx program). * Red Hat FC3: running the testUnits ("rexxTestUnits -r .") will cause a Segmentation fault. This can also be evoked by running the testUnit "./ooRexx.Base.BIF.testUnit".=20 Shall I file a bug report for this? (I speculate that this bug has been fixed already, maybe someone could create the rpm-distro from the repository? If so, I would appreciate a link to it.) =09 Regards, ---rony -------------------------------------------------------- CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, = is for the sole use of the intended recipient(s) and contains = information that is confidential and proprietary to Applied Micro = Circuits Corporation or its subsidiaries. It is to be used solely for = the purpose of furthering the parties' business relationship. All = unauthorized review, use, disclosure or distribution is prohibited. If = you are not the intended recipient, please contact the sender by reply = e-mail and destroy all copies of the original message. |
From: Rony G. F. <Ron...@wu...> - 2007-01-25 10:33:26
|
Hi Mark, > Red Hat FC3: running the testUnits ("rexxTestUnits -r .") will cause a > Segmentation fault. This can also be evoked by running the testUnit > "./ooRexx.Base.BIF.testUnit". > Shall I file a bug report for this? > > No, not if you are using the 3.1.1 release. This is surely the bug > that is fixed in cvs, the same bug Michael reported. (E-mail me off > line if you want me to build you a rpm with the fix incorporated to > make sure.) thank you very much for making a rpm version of the cvs head available for FC6, which does not seg fault. --- Here is a URL which temporarily contains that rpm file, together with a genuine Debian and an Ubutuntu 6.10 package for those who wish to test it. Will remove these packages the moment we have official distributions of them: <http://wi.wu-wien.ac.at/rgf/rexx/misc/ooRexxTempBuilds/>. Regards, ---rony |