From: SourceForge.net <no...@so...> - 2010-01-11 20:36:54
|
Bugs item #2782494, was opened at 2009-04-27 18:25 Message generated for change (Comment added) made by oorexxpert You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=2782494&group_id=119701 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interpreter Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: oorexxpert (oorexxpert) Assigned to: Nobody/Anonymous (nobody) Summary: Hung after control-C Initial Comment: I have a REXX program with a "SIGNAL ON ANY" statement. It appears that if I press cntl-C in rapid succession, the program terminates and I am returned to the DOS prompt. However, if I press cntl-C once, the trace shows the label for the "SIGNAL ON ANY" statement, and wait about 10 seconds, a second cntl-C results in the following display: Error 4: Program interrupted Error 4.1: Program interrupted with HALT condition The program is now hung: additional cntl-C, enter, etc. has no effect. This is on Windows XP using ooRexx400_4349-x86_32.exe I am not certain of the sequence that causes the error because sometimes it works and sometimes it doesn't. ---------------------------------------------------------------------- >Comment By: oorexxpert (oorexxpert) Date: 2010-01-11 15:36 Message: I had just tried it on the latest download of the 4.0.0 release. I will try to create a small test case that reproduces the bug. I have tried several test cases without success. To send the original code that causes the bug would be a major undertaking that might involve hundreds of subroutines. I think, I can start with the original code and start chopping out code until it works correctly. Once I have it isolated, hopefully it will not be too big. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-01-08 21:11 Message: "This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information." This means the interpreter crashed. You originally opened this on one of the 4.0.0 betas, I think. Do you see this current problem on the 4.0.0 release? Also, if you could attach a sample program to reproduce this, or even sometimes reproduce it, that would sure help in debugging. ---------------------------------------------------------------------- Comment By: oorexxpert (oorexxpert) Date: 2010-01-08 14:59 Message: I have not been able to re-create the problem with a small script. However, I do get the following message and I don't know exactly what it means: This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2009-05-02 08:30 Message: I'm going to need a program to help recreate this problem if you wish to get it fixed. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2009-04-27 18:53 Message: We're probably going to need a sample program that demonstrates this problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=2782494&group_id=119701 |