From: SourceForge.net <no...@so...> - 2010-05-11 20:11:14
|
Bugs item #3000154, was opened at 2010-05-11 16:11 Message generated for change (Tracker Item Submitted) made by vmrexx You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&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: LesK (vmrexx) Assigned to: Nobody/Anonymous (nobody) Summary: interpreted sourceline() causes error or crash Initial Comment: ooRexx 4.0.0 Windows 7 Home Premium 64 bit The original bug showed up under THE with sourceline(sigl) not returning any data. I reworked the code to make it simple Rexx and now it crashes ooRexx and Windows goes off looking for a solution. To recreate the problem requires 3 files and SF will only allow me to upload ONE here! I'll have to send you the others. Les ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&group_id=119701 |
From: SourceForge.net <no...@so...> - 2010-05-11 20:44:30
|
Bugs item #3000154, was opened at 2010-05-11 16:11 Message generated for change (Comment added) made by bigrixx You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&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: LesK (vmrexx) Assigned to: Nobody/Anonymous (nobody) Summary: interpreted sourceline() causes error or crash Initial Comment: ooRexx 4.0.0 Windows 7 Home Premium 64 bit The original bug showed up under THE with sourceline(sigl) not returning any data. I reworked the code to make it simple Rexx and now it crashes ooRexx and Windows goes off looking for a solution. To recreate the problem requires 3 files and SF will only allow me to upload ONE here! I'll have to send you the others. Les ---------------------------------------------------------------------- >Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 16:44 Message: do you have the 32-bit or 64-bit version installed? Is there a chance that you're using one of the 4.0 betas rather than the final release? I've run this program on 4.0.0, 4.0.1, and the current development build without any problems. I don't have access to a 64-bit Windows system, so any 64-bit trials will have to wait until Mark Miesfeld returns in a couple of weeks. In the meantime, you might try upgrading to the 4.0.1 release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&group_id=119701 |
From: SourceForge.net <no...@so...> - 2010-05-11 21:14:33
|
Bugs item #3000154, was opened at 2010-05-11 16:11 Message generated for change (Comment added) made by vmrexx You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&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: LesK (vmrexx) Assigned to: Nobody/Anonymous (nobody) Summary: interpreted sourceline() causes error or crash Initial Comment: ooRexx 4.0.0 Windows 7 Home Premium 64 bit The original bug showed up under THE with sourceline(sigl) not returning any data. I reworked the code to make it simple Rexx and now it crashes ooRexx and Windows goes off looking for a solution. To recreate the problem requires 3 files and SF will only allow me to upload ONE here! I'll have to send you the others. Les ---------------------------------------------------------------------- >Comment By: LesK (vmrexx) Date: 2010-05-11 17:14 Message: I'm pretty sure it's the 64 bit version: 5.03 15 June 2009 How can I be sure? ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 16:44 Message: do you have the 32-bit or 64-bit version installed? Is there a chance that you're using one of the 4.0 betas rather than the final release? I've run this program on 4.0.0, 4.0.1, and the current development build without any problems. I don't have access to a 64-bit Windows system, so any 64-bit trials will have to wait until Mark Miesfeld returns in a couple of weeks. In the meantime, you might try upgrading to the 4.0.1 release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&group_id=119701 |
From: SourceForge.net <no...@so...> - 2010-05-11 21:29:24
|
Bugs item #3000154, was opened at 2010-05-11 16:11 Message generated for change (Comment added) made by bigrixx You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&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: LesK (vmrexx) Assigned to: Nobody/Anonymous (nobody) Summary: interpreted sourceline() causes error or crash Initial Comment: ooRexx 4.0.0 Windows 7 Home Premium 64 bit The original bug showed up under THE with sourceline(sigl) not returning any data. I reworked the code to make it simple Rexx and now it crashes ooRexx and Windows goes off looking for a solution. To recreate the problem requires 3 files and SF will only allow me to upload ONE here! I'll have to send you the others. Les ---------------------------------------------------------------------- >Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 17:29 Message: rexx -v will give all of the information about the version you have installed, including the addressing mode. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 17:14 Message: I'm pretty sure it's the 64 bit version: 5.03 15 June 2009 How can I be sure? ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 16:44 Message: do you have the 32-bit or 64-bit version installed? Is there a chance that you're using one of the 4.0 betas rather than the final release? I've run this program on 4.0.0, 4.0.1, and the current development build without any problems. I don't have access to a 64-bit Windows system, so any 64-bit trials will have to wait until Mark Miesfeld returns in a couple of weeks. In the meantime, you might try upgrading to the 4.0.1 release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&group_id=119701 |
From: SourceForge.net <no...@so...> - 2010-05-11 21:37:04
|
Bugs item #3000154, was opened at 2010-05-11 13:11 Message generated for change (Comment added) made by bjskelly You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&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: LesK (vmrexx) Assigned to: Nobody/Anonymous (nobody) Summary: interpreted sourceline() causes error or crash Initial Comment: ooRexx 4.0.0 Windows 7 Home Premium 64 bit The original bug showed up under THE with sourceline(sigl) not returning any data. I reworked the code to make it simple Rexx and now it crashes ooRexx and Windows goes off looking for a solution. To recreate the problem requires 3 files and SF will only allow me to upload ONE here! I'll have to send you the others. Les ---------------------------------------------------------------------- >Comment By: Bruce (bjskelly) Date: 2010-05-11 14:37 Message: You could zip the three files, and upload the zipped file. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 14:29 Message: rexx -v will give all of the information about the version you have installed, including the addressing mode. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 14:14 Message: I'm pretty sure it's the 64 bit version: 5.03 15 June 2009 How can I be sure? ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 13:44 Message: do you have the 32-bit or 64-bit version installed? Is there a chance that you're using one of the 4.0 betas rather than the final release? I've run this program on 4.0.0, 4.0.1, and the current development build without any problems. I don't have access to a 64-bit Windows system, so any 64-bit trials will have to wait until Mark Miesfeld returns in a couple of weeks. In the meantime, you might try upgrading to the 4.0.1 release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&group_id=119701 |
From: SourceForge.net <no...@so...> - 2010-05-11 22:39:20
|
Bugs item #3000154, was opened at 2010-05-11 16:11 Message generated for change (Comment added) made by vmrexx You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&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: LesK (vmrexx) Assigned to: Nobody/Anonymous (nobody) Summary: interpreted sourceline() causes error or crash Initial Comment: ooRexx 4.0.0 Windows 7 Home Premium 64 bit The original bug showed up under THE with sourceline(sigl) not returning any data. I reworked the code to make it simple Rexx and now it crashes ooRexx and Windows goes off looking for a solution. To recreate the problem requires 3 files and SF will only allow me to upload ONE here! I'll have to send you the others. Les ---------------------------------------------------------------------- >Comment By: LesK (vmrexx) Date: 2010-05-11 18:39 Message: It's 32 bit. ---------------------------------------------------------------------- Comment By: Bruce (bjskelly) Date: 2010-05-11 17:37 Message: You could zip the three files, and upload the zipped file. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 17:29 Message: rexx -v will give all of the information about the version you have installed, including the addressing mode. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 17:14 Message: I'm pretty sure it's the 64 bit version: 5.03 15 June 2009 How can I be sure? ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 16:44 Message: do you have the 32-bit or 64-bit version installed? Is there a chance that you're using one of the 4.0 betas rather than the final release? I've run this program on 4.0.0, 4.0.1, and the current development build without any problems. I don't have access to a 64-bit Windows system, so any 64-bit trials will have to wait until Mark Miesfeld returns in a couple of weeks. In the meantime, you might try upgrading to the 4.0.1 release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&group_id=119701 |
From: SourceForge.net <no...@so...> - 2010-05-13 02:46:40
|
Bugs item #3000154, was opened at 2010-05-11 16:11 Message generated for change (Comment added) made by vmrexx You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&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: LesK (vmrexx) Assigned to: Nobody/Anonymous (nobody) Summary: interpreted sourceline() causes error or crash Initial Comment: ooRexx 4.0.0 Windows 7 Home Premium 64 bit The original bug showed up under THE with sourceline(sigl) not returning any data. I reworked the code to make it simple Rexx and now it crashes ooRexx and Windows goes off looking for a solution. To recreate the problem requires 3 files and SF will only allow me to upload ONE here! I'll have to send you the others. Les ---------------------------------------------------------------------- >Comment By: LesK (vmrexx) Date: 2010-05-12 22:46 Message: Fyi, I can't reproduce the problem on my desktop XP system which is also running 4.0.0 I'll leave things as they are on my W7 laptop until the problem can be reproduced by Mark. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 18:39 Message: It's 32 bit. ---------------------------------------------------------------------- Comment By: Bruce (bjskelly) Date: 2010-05-11 17:37 Message: You could zip the three files, and upload the zipped file. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 17:29 Message: rexx -v will give all of the information about the version you have installed, including the addressing mode. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 17:14 Message: I'm pretty sure it's the 64 bit version: 5.03 15 June 2009 How can I be sure? ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 16:44 Message: do you have the 32-bit or 64-bit version installed? Is there a chance that you're using one of the 4.0 betas rather than the final release? I've run this program on 4.0.0, 4.0.1, and the current development build without any problems. I don't have access to a 64-bit Windows system, so any 64-bit trials will have to wait until Mark Miesfeld returns in a couple of weeks. In the meantime, you might try upgrading to the 4.0.1 release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&group_id=119701 |
From: SourceForge.net <no...@so...> - 2010-05-24 16:03:19
|
Bugs item #3000154, was opened at 2010-05-11 13:11 Message generated for change (Comment added) made by miesfeld You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&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: LesK (vmrexx) Assigned to: Nobody/Anonymous (nobody) Summary: interpreted sourceline() causes error or crash Initial Comment: ooRexx 4.0.0 Windows 7 Home Premium 64 bit The original bug showed up under THE with sourceline(sigl) not returning any data. I reworked the code to make it simple Rexx and now it crashes ooRexx and Windows goes off looking for a solution. To recreate the problem requires 3 files and SF will only allow me to upload ONE here! I'll have to send you the others. Les ---------------------------------------------------------------------- >Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 09:03 Message: Les, Would you please upload the other files so I can take a look at this. It's true SourceForge only allows you to upload 1 file at a time. But, you can upload 1 file as many times as you want. So, log back in and upload the 2nd file. Then when that is done, upload the 3rd. Or, as Bruce suggested, put all 3 files in a zip file and upload that. Thanks. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-12 19:46 Message: Fyi, I can't reproduce the problem on my desktop XP system which is also running 4.0.0 I'll leave things as they are on my W7 laptop until the problem can be reproduced by Mark. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 15:39 Message: It's 32 bit. ---------------------------------------------------------------------- Comment By: Bruce (bjskelly) Date: 2010-05-11 14:37 Message: You could zip the three files, and upload the zipped file. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 14:29 Message: rexx -v will give all of the information about the version you have installed, including the addressing mode. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 14:14 Message: I'm pretty sure it's the 64 bit version: 5.03 15 June 2009 How can I be sure? ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 13:44 Message: do you have the 32-bit or 64-bit version installed? Is there a chance that you're using one of the 4.0 betas rather than the final release? I've run this program on 4.0.0, 4.0.1, and the current development build without any problems. I don't have access to a 64-bit Windows system, so any 64-bit trials will have to wait until Mark Miesfeld returns in a couple of weeks. In the meantime, you might try upgrading to the 4.0.1 release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&group_id=119701 |
From: SourceForge.net <no...@so...> - 2010-05-24 22:09:26
|
Bugs item #3000154, was opened at 2010-05-11 16:11 Message generated for change (Comment added) made by vmrexx You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&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: LesK (vmrexx) Assigned to: Nobody/Anonymous (nobody) Summary: interpreted sourceline() causes error or crash Initial Comment: ooRexx 4.0.0 Windows 7 Home Premium 64 bit The original bug showed up under THE with sourceline(sigl) not returning any data. I reworked the code to make it simple Rexx and now it crashes ooRexx and Windows goes off looking for a solution. To recreate the problem requires 3 files and SF will only allow me to upload ONE here! I'll have to send you the others. Les ---------------------------------------------------------------------- >Comment By: LesK (vmrexx) Date: 2010-05-24 18:09 Message: 2nd file ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 12:03 Message: Les, Would you please upload the other files so I can take a look at this. It's true SourceForge only allows you to upload 1 file at a time. But, you can upload 1 file as many times as you want. So, log back in and upload the 2nd file. Then when that is done, upload the 3rd. Or, as Bruce suggested, put all 3 files in a zip file and upload that. Thanks. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-12 22:46 Message: Fyi, I can't reproduce the problem on my desktop XP system which is also running 4.0.0 I'll leave things as they are on my W7 laptop until the problem can be reproduced by Mark. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 18:39 Message: It's 32 bit. ---------------------------------------------------------------------- Comment By: Bruce (bjskelly) Date: 2010-05-11 17:37 Message: You could zip the three files, and upload the zipped file. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 17:29 Message: rexx -v will give all of the information about the version you have installed, including the addressing mode. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 17:14 Message: I'm pretty sure it's the 64 bit version: 5.03 15 June 2009 How can I be sure? ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 16:44 Message: do you have the 32-bit or 64-bit version installed? Is there a chance that you're using one of the 4.0 betas rather than the final release? I've run this program on 4.0.0, 4.0.1, and the current development build without any problems. I don't have access to a 64-bit Windows system, so any 64-bit trials will have to wait until Mark Miesfeld returns in a couple of weeks. In the meantime, you might try upgrading to the 4.0.1 release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&group_id=119701 |
From: SourceForge.net <no...@so...> - 2010-05-24 22:15:41
|
Bugs item #3000154, was opened at 2010-05-11 16:11 Message generated for change (Comment added) made by vmrexx You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&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: LesK (vmrexx) Assigned to: Nobody/Anonymous (nobody) Summary: interpreted sourceline() causes error or crash Initial Comment: ooRexx 4.0.0 Windows 7 Home Premium 64 bit The original bug showed up under THE with sourceline(sigl) not returning any data. I reworked the code to make it simple Rexx and now it crashes ooRexx and Windows goes off looking for a solution. To recreate the problem requires 3 files and SF will only allow me to upload ONE here! I'll have to send you the others. Les ---------------------------------------------------------------------- >Comment By: LesK (vmrexx) Date: 2010-05-24 18:15 Message: Oops! 2nd file. Does SF TRY to make things hard? 'Add a file' has to be clicked on but there is NO indication that it's clickable! ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 18:09 Message: 2nd file ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 12:03 Message: Les, Would you please upload the other files so I can take a look at this. It's true SourceForge only allows you to upload 1 file at a time. But, you can upload 1 file as many times as you want. So, log back in and upload the 2nd file. Then when that is done, upload the 3rd. Or, as Bruce suggested, put all 3 files in a zip file and upload that. Thanks. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-12 22:46 Message: Fyi, I can't reproduce the problem on my desktop XP system which is also running 4.0.0 I'll leave things as they are on my W7 laptop until the problem can be reproduced by Mark. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 18:39 Message: It's 32 bit. ---------------------------------------------------------------------- Comment By: Bruce (bjskelly) Date: 2010-05-11 17:37 Message: You could zip the three files, and upload the zipped file. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 17:29 Message: rexx -v will give all of the information about the version you have installed, including the addressing mode. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 17:14 Message: I'm pretty sure it's the 64 bit version: 5.03 15 June 2009 How can I be sure? ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 16:44 Message: do you have the 32-bit or 64-bit version installed? Is there a chance that you're using one of the 4.0 betas rather than the final release? I've run this program on 4.0.0, 4.0.1, and the current development build without any problems. I don't have access to a 64-bit Windows system, so any 64-bit trials will have to wait until Mark Miesfeld returns in a couple of weeks. In the meantime, you might try upgrading to the 4.0.1 release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&group_id=119701 |
From: SourceForge.net <no...@so...> - 2010-05-24 22:20:35
|
Bugs item #3000154, was opened at 2010-05-11 16:11 Message generated for change (Comment added) made by vmrexx You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&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: LesK (vmrexx) Assigned to: Nobody/Anonymous (nobody) Summary: interpreted sourceline() causes error or crash Initial Comment: ooRexx 4.0.0 Windows 7 Home Premium 64 bit The original bug showed up under THE with sourceline(sigl) not returning any data. I reworked the code to make it simple Rexx and now it crashes ooRexx and Windows goes off looking for a solution. To recreate the problem requires 3 files and SF will only allow me to upload ONE here! I'll have to send you the others. Les ---------------------------------------------------------------------- >Comment By: LesK (vmrexx) Date: 2010-05-24 18:20 Message: All the files are there now. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 18:15 Message: Oops! 2nd file. Does SF TRY to make things hard? 'Add a file' has to be clicked on but there is NO indication that it's clickable! ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 18:09 Message: 2nd file ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 12:03 Message: Les, Would you please upload the other files so I can take a look at this. It's true SourceForge only allows you to upload 1 file at a time. But, you can upload 1 file as many times as you want. So, log back in and upload the 2nd file. Then when that is done, upload the 3rd. Or, as Bruce suggested, put all 3 files in a zip file and upload that. Thanks. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-12 22:46 Message: Fyi, I can't reproduce the problem on my desktop XP system which is also running 4.0.0 I'll leave things as they are on my W7 laptop until the problem can be reproduced by Mark. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 18:39 Message: It's 32 bit. ---------------------------------------------------------------------- Comment By: Bruce (bjskelly) Date: 2010-05-11 17:37 Message: You could zip the three files, and upload the zipped file. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 17:29 Message: rexx -v will give all of the information about the version you have installed, including the addressing mode. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 17:14 Message: I'm pretty sure it's the 64 bit version: 5.03 15 June 2009 How can I be sure? ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 16:44 Message: do you have the 32-bit or 64-bit version installed? Is there a chance that you're using one of the 4.0 betas rather than the final release? I've run this program on 4.0.0, 4.0.1, and the current development build without any problems. I don't have access to a 64-bit Windows system, so any 64-bit trials will have to wait until Mark Miesfeld returns in a couple of weeks. In the meantime, you might try upgrading to the 4.0.1 release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&group_id=119701 |
From: SourceForge.net <no...@so...> - 2010-05-24 22:28:50
|
Bugs item #3000154, was opened at 2010-05-11 13:11 Message generated for change (Comment added) made by miesfeld You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&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: LesK (vmrexx) Assigned to: Nobody/Anonymous (nobody) Summary: interpreted sourceline() causes error or crash Initial Comment: ooRexx 4.0.0 Windows 7 Home Premium 64 bit The original bug showed up under THE with sourceline(sigl) not returning any data. I reworked the code to make it simple Rexx and now it crashes ooRexx and Windows goes off looking for a solution. To recreate the problem requires 3 files and SF will only allow me to upload ONE here! I'll have to send you the others. Les ---------------------------------------------------------------------- >Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 15:28 Message: Thanks Les. I don't know if they *try* to make things hard, or if they just do it by accident. <grin> ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 15:20 Message: All the files are there now. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 15:15 Message: Oops! 2nd file. Does SF TRY to make things hard? 'Add a file' has to be clicked on but there is NO indication that it's clickable! ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 15:09 Message: 2nd file ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 09:03 Message: Les, Would you please upload the other files so I can take a look at this. It's true SourceForge only allows you to upload 1 file at a time. But, you can upload 1 file as many times as you want. So, log back in and upload the 2nd file. Then when that is done, upload the 3rd. Or, as Bruce suggested, put all 3 files in a zip file and upload that. Thanks. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-12 19:46 Message: Fyi, I can't reproduce the problem on my desktop XP system which is also running 4.0.0 I'll leave things as they are on my W7 laptop until the problem can be reproduced by Mark. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 15:39 Message: It's 32 bit. ---------------------------------------------------------------------- Comment By: Bruce (bjskelly) Date: 2010-05-11 14:37 Message: You could zip the three files, and upload the zipped file. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 14:29 Message: rexx -v will give all of the information about the version you have installed, including the addressing mode. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 14:14 Message: I'm pretty sure it's the 64 bit version: 5.03 15 June 2009 How can I be sure? ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 13:44 Message: do you have the 32-bit or 64-bit version installed? Is there a chance that you're using one of the 4.0 betas rather than the final release? I've run this program on 4.0.0, 4.0.1, and the current development build without any problems. I don't have access to a 64-bit Windows system, so any 64-bit trials will have to wait until Mark Miesfeld returns in a couple of weeks. In the meantime, you might try upgrading to the 4.0.1 release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&group_id=119701 |
From: SourceForge.net <no...@so...> - 2010-05-26 05:25:27
|
Bugs item #3000154, was opened at 2010-05-11 13:11 Message generated for change (Comment added) made by miesfeld You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&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: LesK (vmrexx) Assigned to: Nobody/Anonymous (nobody) Summary: interpreted sourceline() causes error or crash Initial Comment: ooRexx 4.0.0 Windows 7 Home Premium 64 bit The original bug showed up under THE with sourceline(sigl) not returning any data. I reworked the code to make it simple Rexx and now it crashes ooRexx and Windows goes off looking for a solution. To recreate the problem requires 3 files and SF will only allow me to upload ONE here! I'll have to send you the others. Les ---------------------------------------------------------------------- >Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-25 22:25 Message: Hi Les, When I run test_config.rex I get this: C:\work.ooRexx\les.bug>test_config.rex 52 *-* ::requires "exception3.rex" Error 43 running C:\work.ooRexx\les.bug\test_config.rex line 52: Routine not found Error 43.901: Could not find routine "exception3.rex" for ::REQUIRES C:\work.ooRexx\les.bug>dir Volume in drive C has no label. Volume Serial Number is BC89-B386 Directory of C:\work.ooRexx\les.bug 05/25/2010 10:19 PM <DIR> . 05/25/2010 10:19 PM <DIR> .. 05/25/2010 10:18 PM 1,822 exception1.rex 05/25/2010 10:19 PM 1,629 rexxla_config.rex 05/25/2010 10:19 PM 1,233 test_config.rex 3 File(s) 4,684 bytes 2 Dir(s) 47,324,303,360 bytes free C:\work.ooRexx\les.bug> If I change the ::requires in test_config.rex to exception1.rex I get this: C:\work.ooRexx\les.bug>test_config.rex 15 *-* parse value exception3() with report_exception /* Get SYNTAX handler */ Error 43 running C:\work.ooRexx\les.bug\test_config.rex line 15: Routine not found Error 43.1: Could not find routine "EXCEPTION3" C:\work.ooRexx\les.bug> If I then go into exception1.rex and change the routine name to: ::routine exception3 public It seems to work fine and I get this output: C:\work.ooRexx\les.bug>test_config.rex REXXLA_CONFIG: Syntax error: Only one argument is allowed. **************RxException*************** CODE =40.4 CONDITION =SYNTAX DESCRIPTION= ERRORTEXT =Incorrect call to routine INSTRUCTION=SIGNAL MESSAGE =Too many arguments in invocation of &1; maximum expected is &2 PACKAGE =a Package POSITION =44 PROGRAM =C:\work.ooRexx\les.bug\rexxla_config.rex PROPAGATED =1 RC =40 SIGL =31 SOURCE =WindowsNT COMMAND C:\work.ooRexx\les.bug\test_config.rex SOURCELINE =data=rexxla_config('registers','tomany') /* Test error conditions */ STACKFRAMES=a List STATUS =OFF TRACEBACK = 31 *-* data=rexxla_config('registers','tomany') /* Test error conditions */ TRACEBACK = 44 *-* raise syntax 40.004 return **************RxException*************** C:\work.ooRexx\les.bug> So, it seems to work fine. This is on Windows 7 Ultimate 64-bit with the 64-bit ooRexx ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 15:28 Message: Thanks Les. I don't know if they *try* to make things hard, or if they just do it by accident. <grin> ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 15:20 Message: All the files are there now. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 15:15 Message: Oops! 2nd file. Does SF TRY to make things hard? 'Add a file' has to be clicked on but there is NO indication that it's clickable! ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 15:09 Message: 2nd file ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 09:03 Message: Les, Would you please upload the other files so I can take a look at this. It's true SourceForge only allows you to upload 1 file at a time. But, you can upload 1 file as many times as you want. So, log back in and upload the 2nd file. Then when that is done, upload the 3rd. Or, as Bruce suggested, put all 3 files in a zip file and upload that. Thanks. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-12 19:46 Message: Fyi, I can't reproduce the problem on my desktop XP system which is also running 4.0.0 I'll leave things as they are on my W7 laptop until the problem can be reproduced by Mark. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 15:39 Message: It's 32 bit. ---------------------------------------------------------------------- Comment By: Bruce (bjskelly) Date: 2010-05-11 14:37 Message: You could zip the three files, and upload the zipped file. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 14:29 Message: rexx -v will give all of the information about the version you have installed, including the addressing mode. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 14:14 Message: I'm pretty sure it's the 64 bit version: 5.03 15 June 2009 How can I be sure? ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 13:44 Message: do you have the 32-bit or 64-bit version installed? Is there a chance that you're using one of the 4.0 betas rather than the final release? I've run this program on 4.0.0, 4.0.1, and the current development build without any problems. I don't have access to a 64-bit Windows system, so any 64-bit trials will have to wait until Mark Miesfeld returns in a couple of weeks. In the meantime, you might try upgrading to the 4.0.1 release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&group_id=119701 |
From: SourceForge.net <no...@so...> - 2010-05-26 09:19:12
|
Bugs item #3000154, was opened at 2010-05-11 16:11 Message generated for change (Comment added) made by bigrixx You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&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: LesK (vmrexx) Assigned to: Nobody/Anonymous (nobody) Summary: interpreted sourceline() causes error or crash Initial Comment: ooRexx 4.0.0 Windows 7 Home Premium 64 bit The original bug showed up under THE with sourceline(sigl) not returning any data. I reworked the code to make it simple Rexx and now it crashes ooRexx and Windows goes off looking for a solution. To recreate the problem requires 3 files and SF will only allow me to upload ONE here! I'll have to send you the others. Les ---------------------------------------------------------------------- >Comment By: Rick McGuire (bigrixx) Date: 2010-05-26 05:19 Message: Mark, I believe Les was running the 32-bit version on 64-bit Vista. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 01:25 Message: Hi Les, When I run test_config.rex I get this: C:\work.ooRexx\les.bug>test_config.rex 52 *-* ::requires "exception3.rex" Error 43 running C:\work.ooRexx\les.bug\test_config.rex line 52: Routine not found Error 43.901: Could not find routine "exception3.rex" for ::REQUIRES C:\work.ooRexx\les.bug>dir Volume in drive C has no label. Volume Serial Number is BC89-B386 Directory of C:\work.ooRexx\les.bug 05/25/2010 10:19 PM <DIR> . 05/25/2010 10:19 PM <DIR> .. 05/25/2010 10:18 PM 1,822 exception1.rex 05/25/2010 10:19 PM 1,629 rexxla_config.rex 05/25/2010 10:19 PM 1,233 test_config.rex 3 File(s) 4,684 bytes 2 Dir(s) 47,324,303,360 bytes free C:\work.ooRexx\les.bug> If I change the ::requires in test_config.rex to exception1.rex I get this: C:\work.ooRexx\les.bug>test_config.rex 15 *-* parse value exception3() with report_exception /* Get SYNTAX handler */ Error 43 running C:\work.ooRexx\les.bug\test_config.rex line 15: Routine not found Error 43.1: Could not find routine "EXCEPTION3" C:\work.ooRexx\les.bug> If I then go into exception1.rex and change the routine name to: ::routine exception3 public It seems to work fine and I get this output: C:\work.ooRexx\les.bug>test_config.rex REXXLA_CONFIG: Syntax error: Only one argument is allowed. **************RxException*************** CODE =40.4 CONDITION =SYNTAX DESCRIPTION= ERRORTEXT =Incorrect call to routine INSTRUCTION=SIGNAL MESSAGE =Too many arguments in invocation of &1; maximum expected is &2 PACKAGE =a Package POSITION =44 PROGRAM =C:\work.ooRexx\les.bug\rexxla_config.rex PROPAGATED =1 RC =40 SIGL =31 SOURCE =WindowsNT COMMAND C:\work.ooRexx\les.bug\test_config.rex SOURCELINE =data=rexxla_config('registers','tomany') /* Test error conditions */ STACKFRAMES=a List STATUS =OFF TRACEBACK = 31 *-* data=rexxla_config('registers','tomany') /* Test error conditions */ TRACEBACK = 44 *-* raise syntax 40.004 return **************RxException*************** C:\work.ooRexx\les.bug> So, it seems to work fine. This is on Windows 7 Ultimate 64-bit with the 64-bit ooRexx ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 18:28 Message: Thanks Les. I don't know if they *try* to make things hard, or if they just do it by accident. <grin> ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 18:20 Message: All the files are there now. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 18:15 Message: Oops! 2nd file. Does SF TRY to make things hard? 'Add a file' has to be clicked on but there is NO indication that it's clickable! ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 18:09 Message: 2nd file ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 12:03 Message: Les, Would you please upload the other files so I can take a look at this. It's true SourceForge only allows you to upload 1 file at a time. But, you can upload 1 file as many times as you want. So, log back in and upload the 2nd file. Then when that is done, upload the 3rd. Or, as Bruce suggested, put all 3 files in a zip file and upload that. Thanks. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-12 22:46 Message: Fyi, I can't reproduce the problem on my desktop XP system which is also running 4.0.0 I'll leave things as they are on my W7 laptop until the problem can be reproduced by Mark. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 18:39 Message: It's 32 bit. ---------------------------------------------------------------------- Comment By: Bruce (bjskelly) Date: 2010-05-11 17:37 Message: You could zip the three files, and upload the zipped file. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 17:29 Message: rexx -v will give all of the information about the version you have installed, including the addressing mode. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 17:14 Message: I'm pretty sure it's the 64 bit version: 5.03 15 June 2009 How can I be sure? ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 16:44 Message: do you have the 32-bit or 64-bit version installed? Is there a chance that you're using one of the 4.0 betas rather than the final release? I've run this program on 4.0.0, 4.0.1, and the current development build without any problems. I don't have access to a 64-bit Windows system, so any 64-bit trials will have to wait until Mark Miesfeld returns in a couple of weeks. In the meantime, you might try upgrading to the 4.0.1 release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&group_id=119701 |
From: SourceForge.net <no...@so...> - 2010-05-26 14:05:50
|
Bugs item #3000154, was opened at 2010-05-11 13:11 Message generated for change (Comment added) made by miesfeld You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&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: LesK (vmrexx) Assigned to: Nobody/Anonymous (nobody) Summary: interpreted sourceline() causes error or crash Initial Comment: ooRexx 4.0.0 Windows 7 Home Premium 64 bit The original bug showed up under THE with sourceline(sigl) not returning any data. I reworked the code to make it simple Rexx and now it crashes ooRexx and Windows goes off looking for a solution. To recreate the problem requires 3 files and SF will only allow me to upload ONE here! I'll have to send you the others. Les ---------------------------------------------------------------------- >Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 07:05 Message: Okay, thanks Rick. I'll try with the 32-bit ooRexx tonight. Les, Are you sure you uploaded the right files? That it is just a name change when you were experimenting? If you have the time, would you download the 3 files from SourceForge and test them to be sure they produce the error on your laptop. If, for some reason they don't, upload a set of files that do produce the error. Remember, you can zip up the 3 files and just upload the 1 zip file if you want. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-26 02:19 Message: Mark, I believe Les was running the 32-bit version on 64-bit Vista. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-25 22:25 Message: Hi Les, When I run test_config.rex I get this: C:\work.ooRexx\les.bug>test_config.rex 52 *-* ::requires "exception3.rex" Error 43 running C:\work.ooRexx\les.bug\test_config.rex line 52: Routine not found Error 43.901: Could not find routine "exception3.rex" for ::REQUIRES C:\work.ooRexx\les.bug>dir Volume in drive C has no label. Volume Serial Number is BC89-B386 Directory of C:\work.ooRexx\les.bug 05/25/2010 10:19 PM <DIR> . 05/25/2010 10:19 PM <DIR> .. 05/25/2010 10:18 PM 1,822 exception1.rex 05/25/2010 10:19 PM 1,629 rexxla_config.rex 05/25/2010 10:19 PM 1,233 test_config.rex 3 File(s) 4,684 bytes 2 Dir(s) 47,324,303,360 bytes free C:\work.ooRexx\les.bug> If I change the ::requires in test_config.rex to exception1.rex I get this: C:\work.ooRexx\les.bug>test_config.rex 15 *-* parse value exception3() with report_exception /* Get SYNTAX handler */ Error 43 running C:\work.ooRexx\les.bug\test_config.rex line 15: Routine not found Error 43.1: Could not find routine "EXCEPTION3" C:\work.ooRexx\les.bug> If I then go into exception1.rex and change the routine name to: ::routine exception3 public It seems to work fine and I get this output: C:\work.ooRexx\les.bug>test_config.rex REXXLA_CONFIG: Syntax error: Only one argument is allowed. **************RxException*************** CODE =40.4 CONDITION =SYNTAX DESCRIPTION= ERRORTEXT =Incorrect call to routine INSTRUCTION=SIGNAL MESSAGE =Too many arguments in invocation of &1; maximum expected is &2 PACKAGE =a Package POSITION =44 PROGRAM =C:\work.ooRexx\les.bug\rexxla_config.rex PROPAGATED =1 RC =40 SIGL =31 SOURCE =WindowsNT COMMAND C:\work.ooRexx\les.bug\test_config.rex SOURCELINE =data=rexxla_config('registers','tomany') /* Test error conditions */ STACKFRAMES=a List STATUS =OFF TRACEBACK = 31 *-* data=rexxla_config('registers','tomany') /* Test error conditions */ TRACEBACK = 44 *-* raise syntax 40.004 return **************RxException*************** C:\work.ooRexx\les.bug> So, it seems to work fine. This is on Windows 7 Ultimate 64-bit with the 64-bit ooRexx ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 15:28 Message: Thanks Les. I don't know if they *try* to make things hard, or if they just do it by accident. <grin> ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 15:20 Message: All the files are there now. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 15:15 Message: Oops! 2nd file. Does SF TRY to make things hard? 'Add a file' has to be clicked on but there is NO indication that it's clickable! ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 15:09 Message: 2nd file ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 09:03 Message: Les, Would you please upload the other files so I can take a look at this. It's true SourceForge only allows you to upload 1 file at a time. But, you can upload 1 file as many times as you want. So, log back in and upload the 2nd file. Then when that is done, upload the 3rd. Or, as Bruce suggested, put all 3 files in a zip file and upload that. Thanks. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-12 19:46 Message: Fyi, I can't reproduce the problem on my desktop XP system which is also running 4.0.0 I'll leave things as they are on my W7 laptop until the problem can be reproduced by Mark. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 15:39 Message: It's 32 bit. ---------------------------------------------------------------------- Comment By: Bruce (bjskelly) Date: 2010-05-11 14:37 Message: You could zip the three files, and upload the zipped file. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 14:29 Message: rexx -v will give all of the information about the version you have installed, including the addressing mode. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 14:14 Message: I'm pretty sure it's the 64 bit version: 5.03 15 June 2009 How can I be sure? ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 13:44 Message: do you have the 32-bit or 64-bit version installed? Is there a chance that you're using one of the 4.0 betas rather than the final release? I've run this program on 4.0.0, 4.0.1, and the current development build without any problems. I don't have access to a 64-bit Windows system, so any 64-bit trials will have to wait until Mark Miesfeld returns in a couple of weeks. In the meantime, you might try upgrading to the 4.0.1 release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&group_id=119701 |
From: SourceForge.net <no...@so...> - 2010-05-26 20:42:47
|
Bugs item #3000154, was opened at 2010-05-11 16:11 Message generated for change (Comment added) made by vmrexx You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&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: LesK (vmrexx) Assigned to: Nobody/Anonymous (nobody) Summary: interpreted sourceline() causes error or crash Initial Comment: ooRexx 4.0.0 Windows 7 Home Premium 64 bit The original bug showed up under THE with sourceline(sigl) not returning any data. I reworked the code to make it simple Rexx and now it crashes ooRexx and Windows goes off looking for a solution. To recreate the problem requires 3 files and SF will only allow me to upload ONE here! I'll have to send you the others. Les ---------------------------------------------------------------------- >Comment By: LesK (vmrexx) Date: 2010-05-26 15:29 Message: Mike, My apologies! I forgot that Michael had sent me a new version of his exception handler and that I had updated the code to use it since he thought it *might* have some bearing on the problem. To clarify: I'm running w7 64bit and 32 bit ooRexx 4.0 and I still get the same symptom, a msg box that says "Open Object Rexx interface has stopped working" Windows is checking for a solution to the problem I don't have to restart or anything. THE is running and continues to run w/o problems. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 10:05 Message: Okay, thanks Rick. I'll try with the 32-bit ooRexx tonight. Les, Are you sure you uploaded the right files? That it is just a name change when you were experimenting? If you have the time, would you download the 3 files from SourceForge and test them to be sure they produce the error on your laptop. If, for some reason they don't, upload a set of files that do produce the error. Remember, you can zip up the 3 files and just upload the 1 zip file if you want. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-26 05:19 Message: Mark, I believe Les was running the 32-bit version on 64-bit Vista. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 01:25 Message: Hi Les, When I run test_config.rex I get this: C:\work.ooRexx\les.bug>test_config.rex 52 *-* ::requires "exception3.rex" Error 43 running C:\work.ooRexx\les.bug\test_config.rex line 52: Routine not found Error 43.901: Could not find routine "exception3.rex" for ::REQUIRES C:\work.ooRexx\les.bug>dir Volume in drive C has no label. Volume Serial Number is BC89-B386 Directory of C:\work.ooRexx\les.bug 05/25/2010 10:19 PM <DIR> . 05/25/2010 10:19 PM <DIR> .. 05/25/2010 10:18 PM 1,822 exception1.rex 05/25/2010 10:19 PM 1,629 rexxla_config.rex 05/25/2010 10:19 PM 1,233 test_config.rex 3 File(s) 4,684 bytes 2 Dir(s) 47,324,303,360 bytes free C:\work.ooRexx\les.bug> If I change the ::requires in test_config.rex to exception1.rex I get this: C:\work.ooRexx\les.bug>test_config.rex 15 *-* parse value exception3() with report_exception /* Get SYNTAX handler */ Error 43 running C:\work.ooRexx\les.bug\test_config.rex line 15: Routine not found Error 43.1: Could not find routine "EXCEPTION3" C:\work.ooRexx\les.bug> If I then go into exception1.rex and change the routine name to: ::routine exception3 public It seems to work fine and I get this output: C:\work.ooRexx\les.bug>test_config.rex REXXLA_CONFIG: Syntax error: Only one argument is allowed. **************RxException*************** CODE =40.4 CONDITION =SYNTAX DESCRIPTION= ERRORTEXT =Incorrect call to routine INSTRUCTION=SIGNAL MESSAGE =Too many arguments in invocation of &1; maximum expected is &2 PACKAGE =a Package POSITION =44 PROGRAM =C:\work.ooRexx\les.bug\rexxla_config.rex PROPAGATED =1 RC =40 SIGL =31 SOURCE =WindowsNT COMMAND C:\work.ooRexx\les.bug\test_config.rex SOURCELINE =data=rexxla_config('registers','tomany') /* Test error conditions */ STACKFRAMES=a List STATUS =OFF TRACEBACK = 31 *-* data=rexxla_config('registers','tomany') /* Test error conditions */ TRACEBACK = 44 *-* raise syntax 40.004 return **************RxException*************** C:\work.ooRexx\les.bug> So, it seems to work fine. This is on Windows 7 Ultimate 64-bit with the 64-bit ooRexx ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 18:28 Message: Thanks Les. I don't know if they *try* to make things hard, or if they just do it by accident. <grin> ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 18:20 Message: All the files are there now. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 18:15 Message: Oops! 2nd file. Does SF TRY to make things hard? 'Add a file' has to be clicked on but there is NO indication that it's clickable! ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 18:09 Message: 2nd file ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 12:03 Message: Les, Would you please upload the other files so I can take a look at this. It's true SourceForge only allows you to upload 1 file at a time. But, you can upload 1 file as many times as you want. So, log back in and upload the 2nd file. Then when that is done, upload the 3rd. Or, as Bruce suggested, put all 3 files in a zip file and upload that. Thanks. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-12 22:46 Message: Fyi, I can't reproduce the problem on my desktop XP system which is also running 4.0.0 I'll leave things as they are on my W7 laptop until the problem can be reproduced by Mark. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 18:39 Message: It's 32 bit. ---------------------------------------------------------------------- Comment By: Bruce (bjskelly) Date: 2010-05-11 17:37 Message: You could zip the three files, and upload the zipped file. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 17:29 Message: rexx -v will give all of the information about the version you have installed, including the addressing mode. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 17:14 Message: I'm pretty sure it's the 64 bit version: 5.03 15 June 2009 How can I be sure? ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 16:44 Message: do you have the 32-bit or 64-bit version installed? Is there a chance that you're using one of the 4.0 betas rather than the final release? I've run this program on 4.0.0, 4.0.1, and the current development build without any problems. I don't have access to a 64-bit Windows system, so any 64-bit trials will have to wait until Mark Miesfeld returns in a couple of weeks. In the meantime, you might try upgrading to the 4.0.1 release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&group_id=119701 |
From: SourceForge.net <no...@so...> - 2010-05-26 20:46:06
|
Bugs item #3000154, was opened at 2010-05-11 16:11 Message generated for change (Comment added) made by vmrexx You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&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: LesK (vmrexx) Assigned to: Nobody/Anonymous (nobody) Summary: interpreted sourceline() causes error or crash Initial Comment: ooRexx 4.0.0 Windows 7 Home Premium 64 bit The original bug showed up under THE with sourceline(sigl) not returning any data. I reworked the code to make it simple Rexx and now it crashes ooRexx and Windows goes off looking for a solution. To recreate the problem requires 3 files and SF will only allow me to upload ONE here! I'll have to send you the others. Les ---------------------------------------------------------------------- >Comment By: LesK (vmrexx) Date: 2010-05-26 15:30 Message: I attached exception3 ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-26 15:29 Message: Mike, My apologies! I forgot that Michael had sent me a new version of his exception handler and that I had updated the code to use it since he thought it *might* have some bearing on the problem. To clarify: I'm running w7 64bit and 32 bit ooRexx 4.0 and I still get the same symptom, a msg box that says "Open Object Rexx interface has stopped working" Windows is checking for a solution to the problem I don't have to restart or anything. THE is running and continues to run w/o problems. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 10:05 Message: Okay, thanks Rick. I'll try with the 32-bit ooRexx tonight. Les, Are you sure you uploaded the right files? That it is just a name change when you were experimenting? If you have the time, would you download the 3 files from SourceForge and test them to be sure they produce the error on your laptop. If, for some reason they don't, upload a set of files that do produce the error. Remember, you can zip up the 3 files and just upload the 1 zip file if you want. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-26 05:19 Message: Mark, I believe Les was running the 32-bit version on 64-bit Vista. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 01:25 Message: Hi Les, When I run test_config.rex I get this: C:\work.ooRexx\les.bug>test_config.rex 52 *-* ::requires "exception3.rex" Error 43 running C:\work.ooRexx\les.bug\test_config.rex line 52: Routine not found Error 43.901: Could not find routine "exception3.rex" for ::REQUIRES C:\work.ooRexx\les.bug>dir Volume in drive C has no label. Volume Serial Number is BC89-B386 Directory of C:\work.ooRexx\les.bug 05/25/2010 10:19 PM <DIR> . 05/25/2010 10:19 PM <DIR> .. 05/25/2010 10:18 PM 1,822 exception1.rex 05/25/2010 10:19 PM 1,629 rexxla_config.rex 05/25/2010 10:19 PM 1,233 test_config.rex 3 File(s) 4,684 bytes 2 Dir(s) 47,324,303,360 bytes free C:\work.ooRexx\les.bug> If I change the ::requires in test_config.rex to exception1.rex I get this: C:\work.ooRexx\les.bug>test_config.rex 15 *-* parse value exception3() with report_exception /* Get SYNTAX handler */ Error 43 running C:\work.ooRexx\les.bug\test_config.rex line 15: Routine not found Error 43.1: Could not find routine "EXCEPTION3" C:\work.ooRexx\les.bug> If I then go into exception1.rex and change the routine name to: ::routine exception3 public It seems to work fine and I get this output: C:\work.ooRexx\les.bug>test_config.rex REXXLA_CONFIG: Syntax error: Only one argument is allowed. **************RxException*************** CODE =40.4 CONDITION =SYNTAX DESCRIPTION= ERRORTEXT =Incorrect call to routine INSTRUCTION=SIGNAL MESSAGE =Too many arguments in invocation of &1; maximum expected is &2 PACKAGE =a Package POSITION =44 PROGRAM =C:\work.ooRexx\les.bug\rexxla_config.rex PROPAGATED =1 RC =40 SIGL =31 SOURCE =WindowsNT COMMAND C:\work.ooRexx\les.bug\test_config.rex SOURCELINE =data=rexxla_config('registers','tomany') /* Test error conditions */ STACKFRAMES=a List STATUS =OFF TRACEBACK = 31 *-* data=rexxla_config('registers','tomany') /* Test error conditions */ TRACEBACK = 44 *-* raise syntax 40.004 return **************RxException*************** C:\work.ooRexx\les.bug> So, it seems to work fine. This is on Windows 7 Ultimate 64-bit with the 64-bit ooRexx ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 18:28 Message: Thanks Les. I don't know if they *try* to make things hard, or if they just do it by accident. <grin> ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 18:20 Message: All the files are there now. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 18:15 Message: Oops! 2nd file. Does SF TRY to make things hard? 'Add a file' has to be clicked on but there is NO indication that it's clickable! ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 18:09 Message: 2nd file ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 12:03 Message: Les, Would you please upload the other files so I can take a look at this. It's true SourceForge only allows you to upload 1 file at a time. But, you can upload 1 file as many times as you want. So, log back in and upload the 2nd file. Then when that is done, upload the 3rd. Or, as Bruce suggested, put all 3 files in a zip file and upload that. Thanks. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-12 22:46 Message: Fyi, I can't reproduce the problem on my desktop XP system which is also running 4.0.0 I'll leave things as they are on my W7 laptop until the problem can be reproduced by Mark. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 18:39 Message: It's 32 bit. ---------------------------------------------------------------------- Comment By: Bruce (bjskelly) Date: 2010-05-11 17:37 Message: You could zip the three files, and upload the zipped file. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 17:29 Message: rexx -v will give all of the information about the version you have installed, including the addressing mode. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 17:14 Message: I'm pretty sure it's the 64 bit version: 5.03 15 June 2009 How can I be sure? ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 16:44 Message: do you have the 32-bit or 64-bit version installed? Is there a chance that you're using one of the 4.0 betas rather than the final release? I've run this program on 4.0.0, 4.0.1, and the current development build without any problems. I don't have access to a 64-bit Windows system, so any 64-bit trials will have to wait until Mark Miesfeld returns in a couple of weeks. In the meantime, you might try upgrading to the 4.0.1 release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&group_id=119701 |
From: SourceForge.net <no...@so...> - 2010-05-26 21:13:00
|
Bugs item #3000154, was opened at 2010-05-11 13:11 Message generated for change (Comment added) made by miesfeld You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&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: LesK (vmrexx) Assigned to: Nobody/Anonymous (nobody) Summary: interpreted sourceline() causes error or crash Initial Comment: ooRexx 4.0.0 Windows 7 Home Premium 64 bit The original bug showed up under THE with sourceline(sigl) not returning any data. I reworked the code to make it simple Rexx and now it crashes ooRexx and Windows goes off looking for a solution. To recreate the problem requires 3 files and SF will only allow me to upload ONE here! I'll have to send you the others. Les ---------------------------------------------------------------------- >Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 13:05 Message: Hi Les, When you see a msg box that says "Open Object Rexx interface has stopped working" in Vista or Windows 7 that basically means the interpreter crashed. So, just to clarify one other thing for me. When you run the program (the 3 files you attached) from the command line do you get the crash? Or, do you only get that when you run the program in THE? If you haven't tried running your example program from the command line, could you try that? I'm just trying to figure out if you only see problems when you are running from within THE, or if the sample program is suppossed to produce the crash all the time, whether you are running THE or not. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-26 12:30 Message: I attached exception3 ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-26 12:29 Message: Mike, My apologies! I forgot that Michael had sent me a new version of his exception handler and that I had updated the code to use it since he thought it *might* have some bearing on the problem. To clarify: I'm running w7 64bit and 32 bit ooRexx 4.0 and I still get the same symptom, a msg box that says "Open Object Rexx interface has stopped working" Windows is checking for a solution to the problem I don't have to restart or anything. THE is running and continues to run w/o problems. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 07:05 Message: Okay, thanks Rick. I'll try with the 32-bit ooRexx tonight. Les, Are you sure you uploaded the right files? That it is just a name change when you were experimenting? If you have the time, would you download the 3 files from SourceForge and test them to be sure they produce the error on your laptop. If, for some reason they don't, upload a set of files that do produce the error. Remember, you can zip up the 3 files and just upload the 1 zip file if you want. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-26 02:19 Message: Mark, I believe Les was running the 32-bit version on 64-bit Vista. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-25 22:25 Message: Hi Les, When I run test_config.rex I get this: C:\work.ooRexx\les.bug>test_config.rex 52 *-* ::requires "exception3.rex" Error 43 running C:\work.ooRexx\les.bug\test_config.rex line 52: Routine not found Error 43.901: Could not find routine "exception3.rex" for ::REQUIRES C:\work.ooRexx\les.bug>dir Volume in drive C has no label. Volume Serial Number is BC89-B386 Directory of C:\work.ooRexx\les.bug 05/25/2010 10:19 PM <DIR> . 05/25/2010 10:19 PM <DIR> .. 05/25/2010 10:18 PM 1,822 exception1.rex 05/25/2010 10:19 PM 1,629 rexxla_config.rex 05/25/2010 10:19 PM 1,233 test_config.rex 3 File(s) 4,684 bytes 2 Dir(s) 47,324,303,360 bytes free C:\work.ooRexx\les.bug> If I change the ::requires in test_config.rex to exception1.rex I get this: C:\work.ooRexx\les.bug>test_config.rex 15 *-* parse value exception3() with report_exception /* Get SYNTAX handler */ Error 43 running C:\work.ooRexx\les.bug\test_config.rex line 15: Routine not found Error 43.1: Could not find routine "EXCEPTION3" C:\work.ooRexx\les.bug> If I then go into exception1.rex and change the routine name to: ::routine exception3 public It seems to work fine and I get this output: C:\work.ooRexx\les.bug>test_config.rex REXXLA_CONFIG: Syntax error: Only one argument is allowed. **************RxException*************** CODE =40.4 CONDITION =SYNTAX DESCRIPTION= ERRORTEXT =Incorrect call to routine INSTRUCTION=SIGNAL MESSAGE =Too many arguments in invocation of &1; maximum expected is &2 PACKAGE =a Package POSITION =44 PROGRAM =C:\work.ooRexx\les.bug\rexxla_config.rex PROPAGATED =1 RC =40 SIGL =31 SOURCE =WindowsNT COMMAND C:\work.ooRexx\les.bug\test_config.rex SOURCELINE =data=rexxla_config('registers','tomany') /* Test error conditions */ STACKFRAMES=a List STATUS =OFF TRACEBACK = 31 *-* data=rexxla_config('registers','tomany') /* Test error conditions */ TRACEBACK = 44 *-* raise syntax 40.004 return **************RxException*************** C:\work.ooRexx\les.bug> So, it seems to work fine. This is on Windows 7 Ultimate 64-bit with the 64-bit ooRexx ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 15:28 Message: Thanks Les. I don't know if they *try* to make things hard, or if they just do it by accident. <grin> ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 15:20 Message: All the files are there now. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 15:15 Message: Oops! 2nd file. Does SF TRY to make things hard? 'Add a file' has to be clicked on but there is NO indication that it's clickable! ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 15:09 Message: 2nd file ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 09:03 Message: Les, Would you please upload the other files so I can take a look at this. It's true SourceForge only allows you to upload 1 file at a time. But, you can upload 1 file as many times as you want. So, log back in and upload the 2nd file. Then when that is done, upload the 3rd. Or, as Bruce suggested, put all 3 files in a zip file and upload that. Thanks. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-12 19:46 Message: Fyi, I can't reproduce the problem on my desktop XP system which is also running 4.0.0 I'll leave things as they are on my W7 laptop until the problem can be reproduced by Mark. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 15:39 Message: It's 32 bit. ---------------------------------------------------------------------- Comment By: Bruce (bjskelly) Date: 2010-05-11 14:37 Message: You could zip the three files, and upload the zipped file. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 14:29 Message: rexx -v will give all of the information about the version you have installed, including the addressing mode. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 14:14 Message: I'm pretty sure it's the 64 bit version: 5.03 15 June 2009 How can I be sure? ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 13:44 Message: do you have the 32-bit or 64-bit version installed? Is there a chance that you're using one of the 4.0 betas rather than the final release? I've run this program on 4.0.0, 4.0.1, and the current development build without any problems. I don't have access to a 64-bit Windows system, so any 64-bit trials will have to wait until Mark Miesfeld returns in a couple of weeks. In the meantime, you might try upgrading to the 4.0.1 release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&group_id=119701 |
From: SourceForge.net <no...@so...> - 2010-05-26 22:04:16
|
Bugs item #3000154, was opened at 2010-05-11 16:11 Message generated for change (Comment added) made by vmrexx You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&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: LesK (vmrexx) Assigned to: Nobody/Anonymous (nobody) Summary: interpreted sourceline() causes error or crash Initial Comment: ooRexx 4.0.0 Windows 7 Home Premium 64 bit The original bug showed up under THE with sourceline(sigl) not returning any data. I reworked the code to make it simple Rexx and now it crashes ooRexx and Windows goes off looking for a solution. To recreate the problem requires 3 files and SF will only allow me to upload ONE here! I'll have to send you the others. Les ---------------------------------------------------------------------- >Comment By: LesK (vmrexx) Date: 2010-05-26 18:04 Message: I initially discovered the problem while running a THE macro. I wrote test_config.rex to make sure that it would fail from the command prompt with the same symptoms w/o the macro, and it did. Since I always have THE up and running, I just now closed it and re-ran the the test from the command line and got the same failure. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 16:05 Message: Hi Les, When you see a msg box that says "Open Object Rexx interface has stopped working" in Vista or Windows 7 that basically means the interpreter crashed. So, just to clarify one other thing for me. When you run the program (the 3 files you attached) from the command line do you get the crash? Or, do you only get that when you run the program in THE? If you haven't tried running your example program from the command line, could you try that? I'm just trying to figure out if you only see problems when you are running from within THE, or if the sample program is suppossed to produce the crash all the time, whether you are running THE or not. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-26 15:30 Message: I attached exception3 ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-26 15:29 Message: Mike, My apologies! I forgot that Michael had sent me a new version of his exception handler and that I had updated the code to use it since he thought it *might* have some bearing on the problem. To clarify: I'm running w7 64bit and 32 bit ooRexx 4.0 and I still get the same symptom, a msg box that says "Open Object Rexx interface has stopped working" Windows is checking for a solution to the problem I don't have to restart or anything. THE is running and continues to run w/o problems. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 10:05 Message: Okay, thanks Rick. I'll try with the 32-bit ooRexx tonight. Les, Are you sure you uploaded the right files? That it is just a name change when you were experimenting? If you have the time, would you download the 3 files from SourceForge and test them to be sure they produce the error on your laptop. If, for some reason they don't, upload a set of files that do produce the error. Remember, you can zip up the 3 files and just upload the 1 zip file if you want. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-26 05:19 Message: Mark, I believe Les was running the 32-bit version on 64-bit Vista. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 01:25 Message: Hi Les, When I run test_config.rex I get this: C:\work.ooRexx\les.bug>test_config.rex 52 *-* ::requires "exception3.rex" Error 43 running C:\work.ooRexx\les.bug\test_config.rex line 52: Routine not found Error 43.901: Could not find routine "exception3.rex" for ::REQUIRES C:\work.ooRexx\les.bug>dir Volume in drive C has no label. Volume Serial Number is BC89-B386 Directory of C:\work.ooRexx\les.bug 05/25/2010 10:19 PM <DIR> . 05/25/2010 10:19 PM <DIR> .. 05/25/2010 10:18 PM 1,822 exception1.rex 05/25/2010 10:19 PM 1,629 rexxla_config.rex 05/25/2010 10:19 PM 1,233 test_config.rex 3 File(s) 4,684 bytes 2 Dir(s) 47,324,303,360 bytes free C:\work.ooRexx\les.bug> If I change the ::requires in test_config.rex to exception1.rex I get this: C:\work.ooRexx\les.bug>test_config.rex 15 *-* parse value exception3() with report_exception /* Get SYNTAX handler */ Error 43 running C:\work.ooRexx\les.bug\test_config.rex line 15: Routine not found Error 43.1: Could not find routine "EXCEPTION3" C:\work.ooRexx\les.bug> If I then go into exception1.rex and change the routine name to: ::routine exception3 public It seems to work fine and I get this output: C:\work.ooRexx\les.bug>test_config.rex REXXLA_CONFIG: Syntax error: Only one argument is allowed. **************RxException*************** CODE =40.4 CONDITION =SYNTAX DESCRIPTION= ERRORTEXT =Incorrect call to routine INSTRUCTION=SIGNAL MESSAGE =Too many arguments in invocation of &1; maximum expected is &2 PACKAGE =a Package POSITION =44 PROGRAM =C:\work.ooRexx\les.bug\rexxla_config.rex PROPAGATED =1 RC =40 SIGL =31 SOURCE =WindowsNT COMMAND C:\work.ooRexx\les.bug\test_config.rex SOURCELINE =data=rexxla_config('registers','tomany') /* Test error conditions */ STACKFRAMES=a List STATUS =OFF TRACEBACK = 31 *-* data=rexxla_config('registers','tomany') /* Test error conditions */ TRACEBACK = 44 *-* raise syntax 40.004 return **************RxException*************** C:\work.ooRexx\les.bug> So, it seems to work fine. This is on Windows 7 Ultimate 64-bit with the 64-bit ooRexx ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 18:28 Message: Thanks Les. I don't know if they *try* to make things hard, or if they just do it by accident. <grin> ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 18:20 Message: All the files are there now. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 18:15 Message: Oops! 2nd file. Does SF TRY to make things hard? 'Add a file' has to be clicked on but there is NO indication that it's clickable! ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 18:09 Message: 2nd file ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 12:03 Message: Les, Would you please upload the other files so I can take a look at this. It's true SourceForge only allows you to upload 1 file at a time. But, you can upload 1 file as many times as you want. So, log back in and upload the 2nd file. Then when that is done, upload the 3rd. Or, as Bruce suggested, put all 3 files in a zip file and upload that. Thanks. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-12 22:46 Message: Fyi, I can't reproduce the problem on my desktop XP system which is also running 4.0.0 I'll leave things as they are on my W7 laptop until the problem can be reproduced by Mark. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 18:39 Message: It's 32 bit. ---------------------------------------------------------------------- Comment By: Bruce (bjskelly) Date: 2010-05-11 17:37 Message: You could zip the three files, and upload the zipped file. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 17:29 Message: rexx -v will give all of the information about the version you have installed, including the addressing mode. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 17:14 Message: I'm pretty sure it's the 64 bit version: 5.03 15 June 2009 How can I be sure? ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 16:44 Message: do you have the 32-bit or 64-bit version installed? Is there a chance that you're using one of the 4.0 betas rather than the final release? I've run this program on 4.0.0, 4.0.1, and the current development build without any problems. I don't have access to a 64-bit Windows system, so any 64-bit trials will have to wait until Mark Miesfeld returns in a couple of weeks. In the meantime, you might try upgrading to the 4.0.1 release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&group_id=119701 |
From: SourceForge.net <no...@so...> - 2010-05-27 03:28:44
|
Bugs item #3000154, was opened at 2010-05-11 13:11 Message generated for change (Comment added) made by miesfeld You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&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: LesK (vmrexx) Assigned to: Nobody/Anonymous (nobody) Summary: interpreted sourceline() causes error or crash Initial Comment: ooRexx 4.0.0 Windows 7 Home Premium 64 bit The original bug showed up under THE with sourceline(sigl) not returning any data. I reworked the code to make it simple Rexx and now it crashes ooRexx and Windows goes off looking for a solution. To recreate the problem requires 3 files and SF will only allow me to upload ONE here! I'll have to send you the others. Les ---------------------------------------------------------------------- >Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 20:28 Message: Yeah, it seems to work just fine for me: C:\work.ooRexx>..\unzip.exe LesBug.zip Archive: LesBug.zip inflating: exception3.rex inflating: rexxla_config.rex inflating: test_config.rex C:\work.ooRexx>test_config.rex REXXLA_CONFIG: Syntax error: Only one argument is allowed. ***********RxException CLASS************ CODE =40.4 CONDITION =SYNTAX DESCRIPTION= ERRORTEXT =Incorrect call to routine INSTRUCTION=SIGNAL MESSAGE =Too many arguments in invocation of &1; maximum expected is &2 POSITION =44 PROGRAM =C:\work.ooRexx\rexxla_config.rex PROPAGATED =1 RC =40 SIGL =31 SOURCE =WindowsNT COMMAND C:\work.ooRexx\test_config.rex SOURCELINE =data=rexxla_config('registers','tomany') /* Test error conditions */ STATUS =OFF TRACEBACK = 44 *-* raise syntax 40.004 return ***********RxException CLASS************ C:\work.ooRexx>rexx -v Open Object Rexx Version 4.0.1 Build date: May 2 2010 Addressing Mode: 32 Copyright (c) IBM Corporation 1995, 2004. Copyright (c) RexxLA 2005-2009. All Rights Reserved. This program and the accompanying materials are made available under the terms of the Common Public License v1.0 which accompanies this distribution. http://www.oorexx.org/license.html C:\work.ooRexx> It doesn't crash and also gets the correct line number (31.) ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-26 15:04 Message: I initially discovered the problem while running a THE macro. I wrote test_config.rex to make sure that it would fail from the command prompt with the same symptoms w/o the macro, and it did. Since I always have THE up and running, I just now closed it and re-ran the the test from the command line and got the same failure. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 13:05 Message: Hi Les, When you see a msg box that says "Open Object Rexx interface has stopped working" in Vista or Windows 7 that basically means the interpreter crashed. So, just to clarify one other thing for me. When you run the program (the 3 files you attached) from the command line do you get the crash? Or, do you only get that when you run the program in THE? If you haven't tried running your example program from the command line, could you try that? I'm just trying to figure out if you only see problems when you are running from within THE, or if the sample program is suppossed to produce the crash all the time, whether you are running THE or not. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-26 12:30 Message: I attached exception3 ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-26 12:29 Message: Mike, My apologies! I forgot that Michael had sent me a new version of his exception handler and that I had updated the code to use it since he thought it *might* have some bearing on the problem. To clarify: I'm running w7 64bit and 32 bit ooRexx 4.0 and I still get the same symptom, a msg box that says "Open Object Rexx interface has stopped working" Windows is checking for a solution to the problem I don't have to restart or anything. THE is running and continues to run w/o problems. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 07:05 Message: Okay, thanks Rick. I'll try with the 32-bit ooRexx tonight. Les, Are you sure you uploaded the right files? That it is just a name change when you were experimenting? If you have the time, would you download the 3 files from SourceForge and test them to be sure they produce the error on your laptop. If, for some reason they don't, upload a set of files that do produce the error. Remember, you can zip up the 3 files and just upload the 1 zip file if you want. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-26 02:19 Message: Mark, I believe Les was running the 32-bit version on 64-bit Vista. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-25 22:25 Message: Hi Les, When I run test_config.rex I get this: C:\work.ooRexx\les.bug>test_config.rex 52 *-* ::requires "exception3.rex" Error 43 running C:\work.ooRexx\les.bug\test_config.rex line 52: Routine not found Error 43.901: Could not find routine "exception3.rex" for ::REQUIRES C:\work.ooRexx\les.bug>dir Volume in drive C has no label. Volume Serial Number is BC89-B386 Directory of C:\work.ooRexx\les.bug 05/25/2010 10:19 PM <DIR> . 05/25/2010 10:19 PM <DIR> .. 05/25/2010 10:18 PM 1,822 exception1.rex 05/25/2010 10:19 PM 1,629 rexxla_config.rex 05/25/2010 10:19 PM 1,233 test_config.rex 3 File(s) 4,684 bytes 2 Dir(s) 47,324,303,360 bytes free C:\work.ooRexx\les.bug> If I change the ::requires in test_config.rex to exception1.rex I get this: C:\work.ooRexx\les.bug>test_config.rex 15 *-* parse value exception3() with report_exception /* Get SYNTAX handler */ Error 43 running C:\work.ooRexx\les.bug\test_config.rex line 15: Routine not found Error 43.1: Could not find routine "EXCEPTION3" C:\work.ooRexx\les.bug> If I then go into exception1.rex and change the routine name to: ::routine exception3 public It seems to work fine and I get this output: C:\work.ooRexx\les.bug>test_config.rex REXXLA_CONFIG: Syntax error: Only one argument is allowed. **************RxException*************** CODE =40.4 CONDITION =SYNTAX DESCRIPTION= ERRORTEXT =Incorrect call to routine INSTRUCTION=SIGNAL MESSAGE =Too many arguments in invocation of &1; maximum expected is &2 PACKAGE =a Package POSITION =44 PROGRAM =C:\work.ooRexx\les.bug\rexxla_config.rex PROPAGATED =1 RC =40 SIGL =31 SOURCE =WindowsNT COMMAND C:\work.ooRexx\les.bug\test_config.rex SOURCELINE =data=rexxla_config('registers','tomany') /* Test error conditions */ STACKFRAMES=a List STATUS =OFF TRACEBACK = 31 *-* data=rexxla_config('registers','tomany') /* Test error conditions */ TRACEBACK = 44 *-* raise syntax 40.004 return **************RxException*************** C:\work.ooRexx\les.bug> So, it seems to work fine. This is on Windows 7 Ultimate 64-bit with the 64-bit ooRexx ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 15:28 Message: Thanks Les. I don't know if they *try* to make things hard, or if they just do it by accident. <grin> ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 15:20 Message: All the files are there now. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 15:15 Message: Oops! 2nd file. Does SF TRY to make things hard? 'Add a file' has to be clicked on but there is NO indication that it's clickable! ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 15:09 Message: 2nd file ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 09:03 Message: Les, Would you please upload the other files so I can take a look at this. It's true SourceForge only allows you to upload 1 file at a time. But, you can upload 1 file as many times as you want. So, log back in and upload the 2nd file. Then when that is done, upload the 3rd. Or, as Bruce suggested, put all 3 files in a zip file and upload that. Thanks. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-12 19:46 Message: Fyi, I can't reproduce the problem on my desktop XP system which is also running 4.0.0 I'll leave things as they are on my W7 laptop until the problem can be reproduced by Mark. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 15:39 Message: It's 32 bit. ---------------------------------------------------------------------- Comment By: Bruce (bjskelly) Date: 2010-05-11 14:37 Message: You could zip the three files, and upload the zipped file. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 14:29 Message: rexx -v will give all of the information about the version you have installed, including the addressing mode. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 14:14 Message: I'm pretty sure it's the 64 bit version: 5.03 15 June 2009 How can I be sure? ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 13:44 Message: do you have the 32-bit or 64-bit version installed? Is there a chance that you're using one of the 4.0 betas rather than the final release? I've run this program on 4.0.0, 4.0.1, and the current development build without any problems. I don't have access to a 64-bit Windows system, so any 64-bit trials will have to wait until Mark Miesfeld returns in a couple of weeks. In the meantime, you might try upgrading to the 4.0.1 release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&group_id=119701 |
From: SourceForge.net <no...@so...> - 2010-05-27 11:45:44
|
Bugs item #3000154, was opened at 2010-05-11 16:11 Message generated for change (Comment added) made by vmrexx You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&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: LesK (vmrexx) Assigned to: Nobody/Anonymous (nobody) Summary: interpreted sourceline() causes error or crash Initial Comment: ooRexx 4.0.0 Windows 7 Home Premium 64 bit The original bug showed up under THE with sourceline(sigl) not returning any data. I reworked the code to make it simple Rexx and now it crashes ooRexx and Windows goes off looking for a solution. To recreate the problem requires 3 files and SF will only allow me to upload ONE here! I'll have to send you the others. Les ---------------------------------------------------------------------- >Comment By: LesK (vmrexx) Date: 2010-05-27 07:45 Message: I'm running 4.-.0 of ooRexx. Should 4.0.1 fix this bug? ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 23:28 Message: Yeah, it seems to work just fine for me: C:\work.ooRexx>..\unzip.exe LesBug.zip Archive: LesBug.zip inflating: exception3.rex inflating: rexxla_config.rex inflating: test_config.rex C:\work.ooRexx>test_config.rex REXXLA_CONFIG: Syntax error: Only one argument is allowed. ***********RxException CLASS************ CODE =40.4 CONDITION =SYNTAX DESCRIPTION= ERRORTEXT =Incorrect call to routine INSTRUCTION=SIGNAL MESSAGE =Too many arguments in invocation of &1; maximum expected is &2 POSITION =44 PROGRAM =C:\work.ooRexx\rexxla_config.rex PROPAGATED =1 RC =40 SIGL =31 SOURCE =WindowsNT COMMAND C:\work.ooRexx\test_config.rex SOURCELINE =data=rexxla_config('registers','tomany') /* Test error conditions */ STATUS =OFF TRACEBACK = 44 *-* raise syntax 40.004 return ***********RxException CLASS************ C:\work.ooRexx>rexx -v Open Object Rexx Version 4.0.1 Build date: May 2 2010 Addressing Mode: 32 Copyright (c) IBM Corporation 1995, 2004. Copyright (c) RexxLA 2005-2009. All Rights Reserved. This program and the accompanying materials are made available under the terms of the Common Public License v1.0 which accompanies this distribution. http://www.oorexx.org/license.html C:\work.ooRexx> It doesn't crash and also gets the correct line number (31.) ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-26 18:04 Message: I initially discovered the problem while running a THE macro. I wrote test_config.rex to make sure that it would fail from the command prompt with the same symptoms w/o the macro, and it did. Since I always have THE up and running, I just now closed it and re-ran the the test from the command line and got the same failure. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 16:05 Message: Hi Les, When you see a msg box that says "Open Object Rexx interface has stopped working" in Vista or Windows 7 that basically means the interpreter crashed. So, just to clarify one other thing for me. When you run the program (the 3 files you attached) from the command line do you get the crash? Or, do you only get that when you run the program in THE? If you haven't tried running your example program from the command line, could you try that? I'm just trying to figure out if you only see problems when you are running from within THE, or if the sample program is suppossed to produce the crash all the time, whether you are running THE or not. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-26 15:30 Message: I attached exception3 ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-26 15:29 Message: Mike, My apologies! I forgot that Michael had sent me a new version of his exception handler and that I had updated the code to use it since he thought it *might* have some bearing on the problem. To clarify: I'm running w7 64bit and 32 bit ooRexx 4.0 and I still get the same symptom, a msg box that says "Open Object Rexx interface has stopped working" Windows is checking for a solution to the problem I don't have to restart or anything. THE is running and continues to run w/o problems. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 10:05 Message: Okay, thanks Rick. I'll try with the 32-bit ooRexx tonight. Les, Are you sure you uploaded the right files? That it is just a name change when you were experimenting? If you have the time, would you download the 3 files from SourceForge and test them to be sure they produce the error on your laptop. If, for some reason they don't, upload a set of files that do produce the error. Remember, you can zip up the 3 files and just upload the 1 zip file if you want. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-26 05:19 Message: Mark, I believe Les was running the 32-bit version on 64-bit Vista. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 01:25 Message: Hi Les, When I run test_config.rex I get this: C:\work.ooRexx\les.bug>test_config.rex 52 *-* ::requires "exception3.rex" Error 43 running C:\work.ooRexx\les.bug\test_config.rex line 52: Routine not found Error 43.901: Could not find routine "exception3.rex" for ::REQUIRES C:\work.ooRexx\les.bug>dir Volume in drive C has no label. Volume Serial Number is BC89-B386 Directory of C:\work.ooRexx\les.bug 05/25/2010 10:19 PM <DIR> . 05/25/2010 10:19 PM <DIR> .. 05/25/2010 10:18 PM 1,822 exception1.rex 05/25/2010 10:19 PM 1,629 rexxla_config.rex 05/25/2010 10:19 PM 1,233 test_config.rex 3 File(s) 4,684 bytes 2 Dir(s) 47,324,303,360 bytes free C:\work.ooRexx\les.bug> If I change the ::requires in test_config.rex to exception1.rex I get this: C:\work.ooRexx\les.bug>test_config.rex 15 *-* parse value exception3() with report_exception /* Get SYNTAX handler */ Error 43 running C:\work.ooRexx\les.bug\test_config.rex line 15: Routine not found Error 43.1: Could not find routine "EXCEPTION3" C:\work.ooRexx\les.bug> If I then go into exception1.rex and change the routine name to: ::routine exception3 public It seems to work fine and I get this output: C:\work.ooRexx\les.bug>test_config.rex REXXLA_CONFIG: Syntax error: Only one argument is allowed. **************RxException*************** CODE =40.4 CONDITION =SYNTAX DESCRIPTION= ERRORTEXT =Incorrect call to routine INSTRUCTION=SIGNAL MESSAGE =Too many arguments in invocation of &1; maximum expected is &2 PACKAGE =a Package POSITION =44 PROGRAM =C:\work.ooRexx\les.bug\rexxla_config.rex PROPAGATED =1 RC =40 SIGL =31 SOURCE =WindowsNT COMMAND C:\work.ooRexx\les.bug\test_config.rex SOURCELINE =data=rexxla_config('registers','tomany') /* Test error conditions */ STACKFRAMES=a List STATUS =OFF TRACEBACK = 31 *-* data=rexxla_config('registers','tomany') /* Test error conditions */ TRACEBACK = 44 *-* raise syntax 40.004 return **************RxException*************** C:\work.ooRexx\les.bug> So, it seems to work fine. This is on Windows 7 Ultimate 64-bit with the 64-bit ooRexx ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 18:28 Message: Thanks Les. I don't know if they *try* to make things hard, or if they just do it by accident. <grin> ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 18:20 Message: All the files are there now. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 18:15 Message: Oops! 2nd file. Does SF TRY to make things hard? 'Add a file' has to be clicked on but there is NO indication that it's clickable! ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 18:09 Message: 2nd file ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 12:03 Message: Les, Would you please upload the other files so I can take a look at this. It's true SourceForge only allows you to upload 1 file at a time. But, you can upload 1 file as many times as you want. So, log back in and upload the 2nd file. Then when that is done, upload the 3rd. Or, as Bruce suggested, put all 3 files in a zip file and upload that. Thanks. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-12 22:46 Message: Fyi, I can't reproduce the problem on my desktop XP system which is also running 4.0.0 I'll leave things as they are on my W7 laptop until the problem can be reproduced by Mark. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 18:39 Message: It's 32 bit. ---------------------------------------------------------------------- Comment By: Bruce (bjskelly) Date: 2010-05-11 17:37 Message: You could zip the three files, and upload the zipped file. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 17:29 Message: rexx -v will give all of the information about the version you have installed, including the addressing mode. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 17:14 Message: I'm pretty sure it's the 64 bit version: 5.03 15 June 2009 How can I be sure? ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 16:44 Message: do you have the 32-bit or 64-bit version installed? Is there a chance that you're using one of the 4.0 betas rather than the final release? I've run this program on 4.0.0, 4.0.1, and the current development build without any problems. I don't have access to a 64-bit Windows system, so any 64-bit trials will have to wait until Mark Miesfeld returns in a couple of weeks. In the meantime, you might try upgrading to the 4.0.1 release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&group_id=119701 |
From: SourceForge.net <no...@so...> - 2010-05-27 11:57:02
|
Bugs item #3000154, was opened at 2010-05-11 16:11 Message generated for change (Comment added) made by bigrixx You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&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: LesK (vmrexx) Assigned to: Nobody/Anonymous (nobody) Summary: interpreted sourceline() causes error or crash Initial Comment: ooRexx 4.0.0 Windows 7 Home Premium 64 bit The original bug showed up under THE with sourceline(sigl) not returning any data. I reworked the code to make it simple Rexx and now it crashes ooRexx and Windows goes off looking for a solution. To recreate the problem requires 3 files and SF will only allow me to upload ONE here! I'll have to send you the others. Les ---------------------------------------------------------------------- >Comment By: Rick McGuire (bigrixx) Date: 2010-05-27 07:57 Message: I suspect you're the only one who can determine that, since we've not been able to recreate this using any combination of versions so far. I suggested some time ago you try upgrading to see if the problem was still there. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-27 07:45 Message: I'm running 4.-.0 of ooRexx. Should 4.0.1 fix this bug? ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 23:28 Message: Yeah, it seems to work just fine for me: C:\work.ooRexx>..\unzip.exe LesBug.zip Archive: LesBug.zip inflating: exception3.rex inflating: rexxla_config.rex inflating: test_config.rex C:\work.ooRexx>test_config.rex REXXLA_CONFIG: Syntax error: Only one argument is allowed. ***********RxException CLASS************ CODE =40.4 CONDITION =SYNTAX DESCRIPTION= ERRORTEXT =Incorrect call to routine INSTRUCTION=SIGNAL MESSAGE =Too many arguments in invocation of &1; maximum expected is &2 POSITION =44 PROGRAM =C:\work.ooRexx\rexxla_config.rex PROPAGATED =1 RC =40 SIGL =31 SOURCE =WindowsNT COMMAND C:\work.ooRexx\test_config.rex SOURCELINE =data=rexxla_config('registers','tomany') /* Test error conditions */ STATUS =OFF TRACEBACK = 44 *-* raise syntax 40.004 return ***********RxException CLASS************ C:\work.ooRexx>rexx -v Open Object Rexx Version 4.0.1 Build date: May 2 2010 Addressing Mode: 32 Copyright (c) IBM Corporation 1995, 2004. Copyright (c) RexxLA 2005-2009. All Rights Reserved. This program and the accompanying materials are made available under the terms of the Common Public License v1.0 which accompanies this distribution. http://www.oorexx.org/license.html C:\work.ooRexx> It doesn't crash and also gets the correct line number (31.) ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-26 18:04 Message: I initially discovered the problem while running a THE macro. I wrote test_config.rex to make sure that it would fail from the command prompt with the same symptoms w/o the macro, and it did. Since I always have THE up and running, I just now closed it and re-ran the the test from the command line and got the same failure. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 16:05 Message: Hi Les, When you see a msg box that says "Open Object Rexx interface has stopped working" in Vista or Windows 7 that basically means the interpreter crashed. So, just to clarify one other thing for me. When you run the program (the 3 files you attached) from the command line do you get the crash? Or, do you only get that when you run the program in THE? If you haven't tried running your example program from the command line, could you try that? I'm just trying to figure out if you only see problems when you are running from within THE, or if the sample program is suppossed to produce the crash all the time, whether you are running THE or not. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-26 15:30 Message: I attached exception3 ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-26 15:29 Message: Mike, My apologies! I forgot that Michael had sent me a new version of his exception handler and that I had updated the code to use it since he thought it *might* have some bearing on the problem. To clarify: I'm running w7 64bit and 32 bit ooRexx 4.0 and I still get the same symptom, a msg box that says "Open Object Rexx interface has stopped working" Windows is checking for a solution to the problem I don't have to restart or anything. THE is running and continues to run w/o problems. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 10:05 Message: Okay, thanks Rick. I'll try with the 32-bit ooRexx tonight. Les, Are you sure you uploaded the right files? That it is just a name change when you were experimenting? If you have the time, would you download the 3 files from SourceForge and test them to be sure they produce the error on your laptop. If, for some reason they don't, upload a set of files that do produce the error. Remember, you can zip up the 3 files and just upload the 1 zip file if you want. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-26 05:19 Message: Mark, I believe Les was running the 32-bit version on 64-bit Vista. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 01:25 Message: Hi Les, When I run test_config.rex I get this: C:\work.ooRexx\les.bug>test_config.rex 52 *-* ::requires "exception3.rex" Error 43 running C:\work.ooRexx\les.bug\test_config.rex line 52: Routine not found Error 43.901: Could not find routine "exception3.rex" for ::REQUIRES C:\work.ooRexx\les.bug>dir Volume in drive C has no label. Volume Serial Number is BC89-B386 Directory of C:\work.ooRexx\les.bug 05/25/2010 10:19 PM <DIR> . 05/25/2010 10:19 PM <DIR> .. 05/25/2010 10:18 PM 1,822 exception1.rex 05/25/2010 10:19 PM 1,629 rexxla_config.rex 05/25/2010 10:19 PM 1,233 test_config.rex 3 File(s) 4,684 bytes 2 Dir(s) 47,324,303,360 bytes free C:\work.ooRexx\les.bug> If I change the ::requires in test_config.rex to exception1.rex I get this: C:\work.ooRexx\les.bug>test_config.rex 15 *-* parse value exception3() with report_exception /* Get SYNTAX handler */ Error 43 running C:\work.ooRexx\les.bug\test_config.rex line 15: Routine not found Error 43.1: Could not find routine "EXCEPTION3" C:\work.ooRexx\les.bug> If I then go into exception1.rex and change the routine name to: ::routine exception3 public It seems to work fine and I get this output: C:\work.ooRexx\les.bug>test_config.rex REXXLA_CONFIG: Syntax error: Only one argument is allowed. **************RxException*************** CODE =40.4 CONDITION =SYNTAX DESCRIPTION= ERRORTEXT =Incorrect call to routine INSTRUCTION=SIGNAL MESSAGE =Too many arguments in invocation of &1; maximum expected is &2 PACKAGE =a Package POSITION =44 PROGRAM =C:\work.ooRexx\les.bug\rexxla_config.rex PROPAGATED =1 RC =40 SIGL =31 SOURCE =WindowsNT COMMAND C:\work.ooRexx\les.bug\test_config.rex SOURCELINE =data=rexxla_config('registers','tomany') /* Test error conditions */ STACKFRAMES=a List STATUS =OFF TRACEBACK = 31 *-* data=rexxla_config('registers','tomany') /* Test error conditions */ TRACEBACK = 44 *-* raise syntax 40.004 return **************RxException*************** C:\work.ooRexx\les.bug> So, it seems to work fine. This is on Windows 7 Ultimate 64-bit with the 64-bit ooRexx ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 18:28 Message: Thanks Les. I don't know if they *try* to make things hard, or if they just do it by accident. <grin> ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 18:20 Message: All the files are there now. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 18:15 Message: Oops! 2nd file. Does SF TRY to make things hard? 'Add a file' has to be clicked on but there is NO indication that it's clickable! ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 18:09 Message: 2nd file ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 12:03 Message: Les, Would you please upload the other files so I can take a look at this. It's true SourceForge only allows you to upload 1 file at a time. But, you can upload 1 file as many times as you want. So, log back in and upload the 2nd file. Then when that is done, upload the 3rd. Or, as Bruce suggested, put all 3 files in a zip file and upload that. Thanks. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-12 22:46 Message: Fyi, I can't reproduce the problem on my desktop XP system which is also running 4.0.0 I'll leave things as they are on my W7 laptop until the problem can be reproduced by Mark. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 18:39 Message: It's 32 bit. ---------------------------------------------------------------------- Comment By: Bruce (bjskelly) Date: 2010-05-11 17:37 Message: You could zip the three files, and upload the zipped file. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 17:29 Message: rexx -v will give all of the information about the version you have installed, including the addressing mode. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 17:14 Message: I'm pretty sure it's the 64 bit version: 5.03 15 June 2009 How can I be sure? ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 16:44 Message: do you have the 32-bit or 64-bit version installed? Is there a chance that you're using one of the 4.0 betas rather than the final release? I've run this program on 4.0.0, 4.0.1, and the current development build without any problems. I don't have access to a 64-bit Windows system, so any 64-bit trials will have to wait until Mark Miesfeld returns in a couple of weeks. In the meantime, you might try upgrading to the 4.0.1 release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&group_id=119701 |
From: SourceForge.net <no...@so...> - 2010-05-27 12:38:50
|
Bugs item #3000154, was opened at 2010-05-11 16:11 Message generated for change (Comment added) made by vmrexx You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&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: LesK (vmrexx) Assigned to: Nobody/Anonymous (nobody) Summary: interpreted sourceline() causes error or crash Initial Comment: ooRexx 4.0.0 Windows 7 Home Premium 64 bit The original bug showed up under THE with sourceline(sigl) not returning any data. I reworked the code to make it simple Rexx and now it crashes ooRexx and Windows goes off looking for a solution. To recreate the problem requires 3 files and SF will only allow me to upload ONE here! I'll have to send you the others. Les ---------------------------------------------------------------------- >Comment By: LesK (vmrexx) Date: 2010-05-27 08:38 Message: I responded saying I'd wait for Mike to try to reproduce it in my environment, which, if he could, would lead to you to discover what was wrong so it could be avoided in the future. Same as I did for IBM before I retired. I know how difficult it is to find bugs on VM, It must be *much* harder on a pc, which is all the more reason to *know* what caused it. If that's not your philosophy, for whatever reason, then so be it. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-27 07:57 Message: I suspect you're the only one who can determine that, since we've not been able to recreate this using any combination of versions so far. I suggested some time ago you try upgrading to see if the problem was still there. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-27 07:45 Message: I'm running 4.-.0 of ooRexx. Should 4.0.1 fix this bug? ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 23:28 Message: Yeah, it seems to work just fine for me: C:\work.ooRexx>..\unzip.exe LesBug.zip Archive: LesBug.zip inflating: exception3.rex inflating: rexxla_config.rex inflating: test_config.rex C:\work.ooRexx>test_config.rex REXXLA_CONFIG: Syntax error: Only one argument is allowed. ***********RxException CLASS************ CODE =40.4 CONDITION =SYNTAX DESCRIPTION= ERRORTEXT =Incorrect call to routine INSTRUCTION=SIGNAL MESSAGE =Too many arguments in invocation of &1; maximum expected is &2 POSITION =44 PROGRAM =C:\work.ooRexx\rexxla_config.rex PROPAGATED =1 RC =40 SIGL =31 SOURCE =WindowsNT COMMAND C:\work.ooRexx\test_config.rex SOURCELINE =data=rexxla_config('registers','tomany') /* Test error conditions */ STATUS =OFF TRACEBACK = 44 *-* raise syntax 40.004 return ***********RxException CLASS************ C:\work.ooRexx>rexx -v Open Object Rexx Version 4.0.1 Build date: May 2 2010 Addressing Mode: 32 Copyright (c) IBM Corporation 1995, 2004. Copyright (c) RexxLA 2005-2009. All Rights Reserved. This program and the accompanying materials are made available under the terms of the Common Public License v1.0 which accompanies this distribution. http://www.oorexx.org/license.html C:\work.ooRexx> It doesn't crash and also gets the correct line number (31.) ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-26 18:04 Message: I initially discovered the problem while running a THE macro. I wrote test_config.rex to make sure that it would fail from the command prompt with the same symptoms w/o the macro, and it did. Since I always have THE up and running, I just now closed it and re-ran the the test from the command line and got the same failure. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 16:05 Message: Hi Les, When you see a msg box that says "Open Object Rexx interface has stopped working" in Vista or Windows 7 that basically means the interpreter crashed. So, just to clarify one other thing for me. When you run the program (the 3 files you attached) from the command line do you get the crash? Or, do you only get that when you run the program in THE? If you haven't tried running your example program from the command line, could you try that? I'm just trying to figure out if you only see problems when you are running from within THE, or if the sample program is suppossed to produce the crash all the time, whether you are running THE or not. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-26 15:30 Message: I attached exception3 ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-26 15:29 Message: Mike, My apologies! I forgot that Michael had sent me a new version of his exception handler and that I had updated the code to use it since he thought it *might* have some bearing on the problem. To clarify: I'm running w7 64bit and 32 bit ooRexx 4.0 and I still get the same symptom, a msg box that says "Open Object Rexx interface has stopped working" Windows is checking for a solution to the problem I don't have to restart or anything. THE is running and continues to run w/o problems. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 10:05 Message: Okay, thanks Rick. I'll try with the 32-bit ooRexx tonight. Les, Are you sure you uploaded the right files? That it is just a name change when you were experimenting? If you have the time, would you download the 3 files from SourceForge and test them to be sure they produce the error on your laptop. If, for some reason they don't, upload a set of files that do produce the error. Remember, you can zip up the 3 files and just upload the 1 zip file if you want. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-26 05:19 Message: Mark, I believe Les was running the 32-bit version on 64-bit Vista. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 01:25 Message: Hi Les, When I run test_config.rex I get this: C:\work.ooRexx\les.bug>test_config.rex 52 *-* ::requires "exception3.rex" Error 43 running C:\work.ooRexx\les.bug\test_config.rex line 52: Routine not found Error 43.901: Could not find routine "exception3.rex" for ::REQUIRES C:\work.ooRexx\les.bug>dir Volume in drive C has no label. Volume Serial Number is BC89-B386 Directory of C:\work.ooRexx\les.bug 05/25/2010 10:19 PM <DIR> . 05/25/2010 10:19 PM <DIR> .. 05/25/2010 10:18 PM 1,822 exception1.rex 05/25/2010 10:19 PM 1,629 rexxla_config.rex 05/25/2010 10:19 PM 1,233 test_config.rex 3 File(s) 4,684 bytes 2 Dir(s) 47,324,303,360 bytes free C:\work.ooRexx\les.bug> If I change the ::requires in test_config.rex to exception1.rex I get this: C:\work.ooRexx\les.bug>test_config.rex 15 *-* parse value exception3() with report_exception /* Get SYNTAX handler */ Error 43 running C:\work.ooRexx\les.bug\test_config.rex line 15: Routine not found Error 43.1: Could not find routine "EXCEPTION3" C:\work.ooRexx\les.bug> If I then go into exception1.rex and change the routine name to: ::routine exception3 public It seems to work fine and I get this output: C:\work.ooRexx\les.bug>test_config.rex REXXLA_CONFIG: Syntax error: Only one argument is allowed. **************RxException*************** CODE =40.4 CONDITION =SYNTAX DESCRIPTION= ERRORTEXT =Incorrect call to routine INSTRUCTION=SIGNAL MESSAGE =Too many arguments in invocation of &1; maximum expected is &2 PACKAGE =a Package POSITION =44 PROGRAM =C:\work.ooRexx\les.bug\rexxla_config.rex PROPAGATED =1 RC =40 SIGL =31 SOURCE =WindowsNT COMMAND C:\work.ooRexx\les.bug\test_config.rex SOURCELINE =data=rexxla_config('registers','tomany') /* Test error conditions */ STACKFRAMES=a List STATUS =OFF TRACEBACK = 31 *-* data=rexxla_config('registers','tomany') /* Test error conditions */ TRACEBACK = 44 *-* raise syntax 40.004 return **************RxException*************** C:\work.ooRexx\les.bug> So, it seems to work fine. This is on Windows 7 Ultimate 64-bit with the 64-bit ooRexx ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 18:28 Message: Thanks Les. I don't know if they *try* to make things hard, or if they just do it by accident. <grin> ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 18:20 Message: All the files are there now. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 18:15 Message: Oops! 2nd file. Does SF TRY to make things hard? 'Add a file' has to be clicked on but there is NO indication that it's clickable! ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 18:09 Message: 2nd file ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 12:03 Message: Les, Would you please upload the other files so I can take a look at this. It's true SourceForge only allows you to upload 1 file at a time. But, you can upload 1 file as many times as you want. So, log back in and upload the 2nd file. Then when that is done, upload the 3rd. Or, as Bruce suggested, put all 3 files in a zip file and upload that. Thanks. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-12 22:46 Message: Fyi, I can't reproduce the problem on my desktop XP system which is also running 4.0.0 I'll leave things as they are on my W7 laptop until the problem can be reproduced by Mark. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 18:39 Message: It's 32 bit. ---------------------------------------------------------------------- Comment By: Bruce (bjskelly) Date: 2010-05-11 17:37 Message: You could zip the three files, and upload the zipped file. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 17:29 Message: rexx -v will give all of the information about the version you have installed, including the addressing mode. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 17:14 Message: I'm pretty sure it's the 64 bit version: 5.03 15 June 2009 How can I be sure? ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 16:44 Message: do you have the 32-bit or 64-bit version installed? Is there a chance that you're using one of the 4.0 betas rather than the final release? I've run this program on 4.0.0, 4.0.1, and the current development build without any problems. I don't have access to a 64-bit Windows system, so any 64-bit trials will have to wait until Mark Miesfeld returns in a couple of weeks. In the meantime, you might try upgrading to the 4.0.1 release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&group_id=119701 |
From: SourceForge.net <no...@so...> - 2010-05-27 12:46:45
|
Bugs item #3000154, was opened at 2010-05-11 16:11 Message generated for change (Comment added) made by bigrixx You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&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: LesK (vmrexx) Assigned to: Nobody/Anonymous (nobody) Summary: interpreted sourceline() causes error or crash Initial Comment: ooRexx 4.0.0 Windows 7 Home Premium 64 bit The original bug showed up under THE with sourceline(sigl) not returning any data. I reworked the code to make it simple Rexx and now it crashes ooRexx and Windows goes off looking for a solution. To recreate the problem requires 3 files and SF will only allow me to upload ONE here! I'll have to send you the others. Les ---------------------------------------------------------------------- >Comment By: Rick McGuire (bigrixx) Date: 2010-05-27 08:46 Message: Les, could you attach the full results of running rexx -v so I can see exactly what version you are running? ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-27 08:38 Message: I responded saying I'd wait for Mike to try to reproduce it in my environment, which, if he could, would lead to you to discover what was wrong so it could be avoided in the future. Same as I did for IBM before I retired. I know how difficult it is to find bugs on VM, It must be *much* harder on a pc, which is all the more reason to *know* what caused it. If that's not your philosophy, for whatever reason, then so be it. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-27 07:57 Message: I suspect you're the only one who can determine that, since we've not been able to recreate this using any combination of versions so far. I suggested some time ago you try upgrading to see if the problem was still there. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-27 07:45 Message: I'm running 4.-.0 of ooRexx. Should 4.0.1 fix this bug? ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 23:28 Message: Yeah, it seems to work just fine for me: C:\work.ooRexx>..\unzip.exe LesBug.zip Archive: LesBug.zip inflating: exception3.rex inflating: rexxla_config.rex inflating: test_config.rex C:\work.ooRexx>test_config.rex REXXLA_CONFIG: Syntax error: Only one argument is allowed. ***********RxException CLASS************ CODE =40.4 CONDITION =SYNTAX DESCRIPTION= ERRORTEXT =Incorrect call to routine INSTRUCTION=SIGNAL MESSAGE =Too many arguments in invocation of &1; maximum expected is &2 POSITION =44 PROGRAM =C:\work.ooRexx\rexxla_config.rex PROPAGATED =1 RC =40 SIGL =31 SOURCE =WindowsNT COMMAND C:\work.ooRexx\test_config.rex SOURCELINE =data=rexxla_config('registers','tomany') /* Test error conditions */ STATUS =OFF TRACEBACK = 44 *-* raise syntax 40.004 return ***********RxException CLASS************ C:\work.ooRexx>rexx -v Open Object Rexx Version 4.0.1 Build date: May 2 2010 Addressing Mode: 32 Copyright (c) IBM Corporation 1995, 2004. Copyright (c) RexxLA 2005-2009. All Rights Reserved. This program and the accompanying materials are made available under the terms of the Common Public License v1.0 which accompanies this distribution. http://www.oorexx.org/license.html C:\work.ooRexx> It doesn't crash and also gets the correct line number (31.) ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-26 18:04 Message: I initially discovered the problem while running a THE macro. I wrote test_config.rex to make sure that it would fail from the command prompt with the same symptoms w/o the macro, and it did. Since I always have THE up and running, I just now closed it and re-ran the the test from the command line and got the same failure. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 16:05 Message: Hi Les, When you see a msg box that says "Open Object Rexx interface has stopped working" in Vista or Windows 7 that basically means the interpreter crashed. So, just to clarify one other thing for me. When you run the program (the 3 files you attached) from the command line do you get the crash? Or, do you only get that when you run the program in THE? If you haven't tried running your example program from the command line, could you try that? I'm just trying to figure out if you only see problems when you are running from within THE, or if the sample program is suppossed to produce the crash all the time, whether you are running THE or not. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-26 15:30 Message: I attached exception3 ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-26 15:29 Message: Mike, My apologies! I forgot that Michael had sent me a new version of his exception handler and that I had updated the code to use it since he thought it *might* have some bearing on the problem. To clarify: I'm running w7 64bit and 32 bit ooRexx 4.0 and I still get the same symptom, a msg box that says "Open Object Rexx interface has stopped working" Windows is checking for a solution to the problem I don't have to restart or anything. THE is running and continues to run w/o problems. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 10:05 Message: Okay, thanks Rick. I'll try with the 32-bit ooRexx tonight. Les, Are you sure you uploaded the right files? That it is just a name change when you were experimenting? If you have the time, would you download the 3 files from SourceForge and test them to be sure they produce the error on your laptop. If, for some reason they don't, upload a set of files that do produce the error. Remember, you can zip up the 3 files and just upload the 1 zip file if you want. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-26 05:19 Message: Mark, I believe Les was running the 32-bit version on 64-bit Vista. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 01:25 Message: Hi Les, When I run test_config.rex I get this: C:\work.ooRexx\les.bug>test_config.rex 52 *-* ::requires "exception3.rex" Error 43 running C:\work.ooRexx\les.bug\test_config.rex line 52: Routine not found Error 43.901: Could not find routine "exception3.rex" for ::REQUIRES C:\work.ooRexx\les.bug>dir Volume in drive C has no label. Volume Serial Number is BC89-B386 Directory of C:\work.ooRexx\les.bug 05/25/2010 10:19 PM <DIR> . 05/25/2010 10:19 PM <DIR> .. 05/25/2010 10:18 PM 1,822 exception1.rex 05/25/2010 10:19 PM 1,629 rexxla_config.rex 05/25/2010 10:19 PM 1,233 test_config.rex 3 File(s) 4,684 bytes 2 Dir(s) 47,324,303,360 bytes free C:\work.ooRexx\les.bug> If I change the ::requires in test_config.rex to exception1.rex I get this: C:\work.ooRexx\les.bug>test_config.rex 15 *-* parse value exception3() with report_exception /* Get SYNTAX handler */ Error 43 running C:\work.ooRexx\les.bug\test_config.rex line 15: Routine not found Error 43.1: Could not find routine "EXCEPTION3" C:\work.ooRexx\les.bug> If I then go into exception1.rex and change the routine name to: ::routine exception3 public It seems to work fine and I get this output: C:\work.ooRexx\les.bug>test_config.rex REXXLA_CONFIG: Syntax error: Only one argument is allowed. **************RxException*************** CODE =40.4 CONDITION =SYNTAX DESCRIPTION= ERRORTEXT =Incorrect call to routine INSTRUCTION=SIGNAL MESSAGE =Too many arguments in invocation of &1; maximum expected is &2 PACKAGE =a Package POSITION =44 PROGRAM =C:\work.ooRexx\les.bug\rexxla_config.rex PROPAGATED =1 RC =40 SIGL =31 SOURCE =WindowsNT COMMAND C:\work.ooRexx\les.bug\test_config.rex SOURCELINE =data=rexxla_config('registers','tomany') /* Test error conditions */ STACKFRAMES=a List STATUS =OFF TRACEBACK = 31 *-* data=rexxla_config('registers','tomany') /* Test error conditions */ TRACEBACK = 44 *-* raise syntax 40.004 return **************RxException*************** C:\work.ooRexx\les.bug> So, it seems to work fine. This is on Windows 7 Ultimate 64-bit with the 64-bit ooRexx ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 18:28 Message: Thanks Les. I don't know if they *try* to make things hard, or if they just do it by accident. <grin> ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 18:20 Message: All the files are there now. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 18:15 Message: Oops! 2nd file. Does SF TRY to make things hard? 'Add a file' has to be clicked on but there is NO indication that it's clickable! ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 18:09 Message: 2nd file ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 12:03 Message: Les, Would you please upload the other files so I can take a look at this. It's true SourceForge only allows you to upload 1 file at a time. But, you can upload 1 file as many times as you want. So, log back in and upload the 2nd file. Then when that is done, upload the 3rd. Or, as Bruce suggested, put all 3 files in a zip file and upload that. Thanks. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-12 22:46 Message: Fyi, I can't reproduce the problem on my desktop XP system which is also running 4.0.0 I'll leave things as they are on my W7 laptop until the problem can be reproduced by Mark. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 18:39 Message: It's 32 bit. ---------------------------------------------------------------------- Comment By: Bruce (bjskelly) Date: 2010-05-11 17:37 Message: You could zip the three files, and upload the zipped file. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 17:29 Message: rexx -v will give all of the information about the version you have installed, including the addressing mode. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 17:14 Message: I'm pretty sure it's the 64 bit version: 5.03 15 June 2009 How can I be sure? ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 16:44 Message: do you have the 32-bit or 64-bit version installed? Is there a chance that you're using one of the 4.0 betas rather than the final release? I've run this program on 4.0.0, 4.0.1, and the current development build without any problems. I don't have access to a 64-bit Windows system, so any 64-bit trials will have to wait until Mark Miesfeld returns in a couple of weeks. In the meantime, you might try upgrading to the 4.0.1 release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&group_id=119701 |
From: SourceForge.net <no...@so...> - 2010-05-27 17:08:01
|
Bugs item #3000154, was opened at 2010-05-11 16:11 Message generated for change (Comment added) made by vmrexx You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&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: LesK (vmrexx) Assigned to: Nobody/Anonymous (nobody) Summary: interpreted sourceline() causes error or crash Initial Comment: ooRexx 4.0.0 Windows 7 Home Premium 64 bit The original bug showed up under THE with sourceline(sigl) not returning any data. I reworked the code to make it simple Rexx and now it crashes ooRexx and Windows goes off looking for a solution. To recreate the problem requires 3 files and SF will only allow me to upload ONE here! I'll have to send you the others. Les ---------------------------------------------------------------------- >Comment By: LesK (vmrexx) Date: 2010-05-27 13:08 Message: Microsoft Windows [Version 6.1.7600] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Les Koehler>rexx -v Open Object Rexx Version 4.0.0 Build date: Jun 15 2009 Addressing Mode: 32 Copyright (c) IBM Corporation 1995, 2004. Copyright (c) RexxLA 2005-2009. All Rights Reserved. This program and the accompanying materials are made available under the terms of the Common Public License v1.0 which accompanies this distribution. http://www.oorexx.org/license.html C:\Users\Les Koehler> ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-27 08:46 Message: Les, could you attach the full results of running rexx -v so I can see exactly what version you are running? ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-27 08:38 Message: I responded saying I'd wait for Mike to try to reproduce it in my environment, which, if he could, would lead to you to discover what was wrong so it could be avoided in the future. Same as I did for IBM before I retired. I know how difficult it is to find bugs on VM, It must be *much* harder on a pc, which is all the more reason to *know* what caused it. If that's not your philosophy, for whatever reason, then so be it. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-27 07:57 Message: I suspect you're the only one who can determine that, since we've not been able to recreate this using any combination of versions so far. I suggested some time ago you try upgrading to see if the problem was still there. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-27 07:45 Message: I'm running 4.-.0 of ooRexx. Should 4.0.1 fix this bug? ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 23:28 Message: Yeah, it seems to work just fine for me: C:\work.ooRexx>..\unzip.exe LesBug.zip Archive: LesBug.zip inflating: exception3.rex inflating: rexxla_config.rex inflating: test_config.rex C:\work.ooRexx>test_config.rex REXXLA_CONFIG: Syntax error: Only one argument is allowed. ***********RxException CLASS************ CODE =40.4 CONDITION =SYNTAX DESCRIPTION= ERRORTEXT =Incorrect call to routine INSTRUCTION=SIGNAL MESSAGE =Too many arguments in invocation of &1; maximum expected is &2 POSITION =44 PROGRAM =C:\work.ooRexx\rexxla_config.rex PROPAGATED =1 RC =40 SIGL =31 SOURCE =WindowsNT COMMAND C:\work.ooRexx\test_config.rex SOURCELINE =data=rexxla_config('registers','tomany') /* Test error conditions */ STATUS =OFF TRACEBACK = 44 *-* raise syntax 40.004 return ***********RxException CLASS************ C:\work.ooRexx>rexx -v Open Object Rexx Version 4.0.1 Build date: May 2 2010 Addressing Mode: 32 Copyright (c) IBM Corporation 1995, 2004. Copyright (c) RexxLA 2005-2009. All Rights Reserved. This program and the accompanying materials are made available under the terms of the Common Public License v1.0 which accompanies this distribution. http://www.oorexx.org/license.html C:\work.ooRexx> It doesn't crash and also gets the correct line number (31.) ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-26 18:04 Message: I initially discovered the problem while running a THE macro. I wrote test_config.rex to make sure that it would fail from the command prompt with the same symptoms w/o the macro, and it did. Since I always have THE up and running, I just now closed it and re-ran the the test from the command line and got the same failure. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 16:05 Message: Hi Les, When you see a msg box that says "Open Object Rexx interface has stopped working" in Vista or Windows 7 that basically means the interpreter crashed. So, just to clarify one other thing for me. When you run the program (the 3 files you attached) from the command line do you get the crash? Or, do you only get that when you run the program in THE? If you haven't tried running your example program from the command line, could you try that? I'm just trying to figure out if you only see problems when you are running from within THE, or if the sample program is suppossed to produce the crash all the time, whether you are running THE or not. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-26 15:30 Message: I attached exception3 ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-26 15:29 Message: Mike, My apologies! I forgot that Michael had sent me a new version of his exception handler and that I had updated the code to use it since he thought it *might* have some bearing on the problem. To clarify: I'm running w7 64bit and 32 bit ooRexx 4.0 and I still get the same symptom, a msg box that says "Open Object Rexx interface has stopped working" Windows is checking for a solution to the problem I don't have to restart or anything. THE is running and continues to run w/o problems. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 10:05 Message: Okay, thanks Rick. I'll try with the 32-bit ooRexx tonight. Les, Are you sure you uploaded the right files? That it is just a name change when you were experimenting? If you have the time, would you download the 3 files from SourceForge and test them to be sure they produce the error on your laptop. If, for some reason they don't, upload a set of files that do produce the error. Remember, you can zip up the 3 files and just upload the 1 zip file if you want. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-26 05:19 Message: Mark, I believe Les was running the 32-bit version on 64-bit Vista. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-26 01:25 Message: Hi Les, When I run test_config.rex I get this: C:\work.ooRexx\les.bug>test_config.rex 52 *-* ::requires "exception3.rex" Error 43 running C:\work.ooRexx\les.bug\test_config.rex line 52: Routine not found Error 43.901: Could not find routine "exception3.rex" for ::REQUIRES C:\work.ooRexx\les.bug>dir Volume in drive C has no label. Volume Serial Number is BC89-B386 Directory of C:\work.ooRexx\les.bug 05/25/2010 10:19 PM <DIR> . 05/25/2010 10:19 PM <DIR> .. 05/25/2010 10:18 PM 1,822 exception1.rex 05/25/2010 10:19 PM 1,629 rexxla_config.rex 05/25/2010 10:19 PM 1,233 test_config.rex 3 File(s) 4,684 bytes 2 Dir(s) 47,324,303,360 bytes free C:\work.ooRexx\les.bug> If I change the ::requires in test_config.rex to exception1.rex I get this: C:\work.ooRexx\les.bug>test_config.rex 15 *-* parse value exception3() with report_exception /* Get SYNTAX handler */ Error 43 running C:\work.ooRexx\les.bug\test_config.rex line 15: Routine not found Error 43.1: Could not find routine "EXCEPTION3" C:\work.ooRexx\les.bug> If I then go into exception1.rex and change the routine name to: ::routine exception3 public It seems to work fine and I get this output: C:\work.ooRexx\les.bug>test_config.rex REXXLA_CONFIG: Syntax error: Only one argument is allowed. **************RxException*************** CODE =40.4 CONDITION =SYNTAX DESCRIPTION= ERRORTEXT =Incorrect call to routine INSTRUCTION=SIGNAL MESSAGE =Too many arguments in invocation of &1; maximum expected is &2 PACKAGE =a Package POSITION =44 PROGRAM =C:\work.ooRexx\les.bug\rexxla_config.rex PROPAGATED =1 RC =40 SIGL =31 SOURCE =WindowsNT COMMAND C:\work.ooRexx\les.bug\test_config.rex SOURCELINE =data=rexxla_config('registers','tomany') /* Test error conditions */ STACKFRAMES=a List STATUS =OFF TRACEBACK = 31 *-* data=rexxla_config('registers','tomany') /* Test error conditions */ TRACEBACK = 44 *-* raise syntax 40.004 return **************RxException*************** C:\work.ooRexx\les.bug> So, it seems to work fine. This is on Windows 7 Ultimate 64-bit with the 64-bit ooRexx ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 18:28 Message: Thanks Les. I don't know if they *try* to make things hard, or if they just do it by accident. <grin> ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 18:20 Message: All the files are there now. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 18:15 Message: Oops! 2nd file. Does SF TRY to make things hard? 'Add a file' has to be clicked on but there is NO indication that it's clickable! ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-24 18:09 Message: 2nd file ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2010-05-24 12:03 Message: Les, Would you please upload the other files so I can take a look at this. It's true SourceForge only allows you to upload 1 file at a time. But, you can upload 1 file as many times as you want. So, log back in and upload the 2nd file. Then when that is done, upload the 3rd. Or, as Bruce suggested, put all 3 files in a zip file and upload that. Thanks. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-12 22:46 Message: Fyi, I can't reproduce the problem on my desktop XP system which is also running 4.0.0 I'll leave things as they are on my W7 laptop until the problem can be reproduced by Mark. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 18:39 Message: It's 32 bit. ---------------------------------------------------------------------- Comment By: Bruce (bjskelly) Date: 2010-05-11 17:37 Message: You could zip the three files, and upload the zipped file. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 17:29 Message: rexx -v will give all of the information about the version you have installed, including the addressing mode. ---------------------------------------------------------------------- Comment By: LesK (vmrexx) Date: 2010-05-11 17:14 Message: I'm pretty sure it's the 64 bit version: 5.03 15 June 2009 How can I be sure? ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2010-05-11 16:44 Message: do you have the 32-bit or 64-bit version installed? Is there a chance that you're using one of the 4.0 betas rather than the final release? I've run this program on 4.0.0, 4.0.1, and the current development build without any problems. I don't have access to a 64-bit Windows system, so any 64-bit trials will have to wait until Mark Miesfeld returns in a couple of weeks. In the meantime, you might try upgrading to the 4.0.1 release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3000154&group_id=119701 |