#646 Hung after control-C


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.


  • Rick McGuire

    Rick McGuire - 2009-04-27

    We're probably going to need a sample program that demonstrates this problem.

  • Rick McGuire

    Rick McGuire - 2009-05-02

    I'm going to need a program to help recreate this problem if you wish to get it fixed.

  • oorexxpert

    oorexxpert - 2010-01-08

    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.

  • Mark Miesfeld

    Mark Miesfeld - 2010-01-09

    "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.

  • oorexxpert

    oorexxpert - 2010-01-11

    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.

  • oorexxpert

    oorexxpert - 2010-01-11

    I have located the cause of the failure! It seems that deep in the code, I set a local environment variable by the name of MONITOR. That name, of course, is already being used by the "monitor class". In previous versions of ooREXX, this was never a problem. Now it seems to be a problem even though we never use the monitor class.

    Looks like I got a lot of fixing up to do.


  • Mark Miesfeld

    Mark Miesfeld - 2010-08-12

    Hi John,

    What's the status with this bug with you?

    Were you able to make changes that eliminated the problem completely for you?

    Do you think there is still a bug here in the interpreter?

    You also brough up a crash you were seeing. Can you reproduce that crash at all so we could take a look at it?

  • Rick McGuire

    Rick McGuire - 2013-11-20

    Closing this as we never received additional means of recreating.

  • Rick McGuire

    Rick McGuire - 2013-11-20
    • status: open --> wont-fix
    • Pending work items: --> none
    • Group: --> None


Cancel  Add attachments

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks