Re: [Oorexx-devel] Build 4507 -> 4521
OK, this is also in 4525. I have narrowed it down -- it dies on the second call to sysfileexists -- will add more details and scenario to tracker. Mike - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Mike Cowlishaw, IBM Fellow http://bit.ly/mfc IBM UK (MP8), PO Box 31, Birmingham Road, Warwick, CV34 5JL Rick McGuire wrote on 27/04/2009 20:16:03: > Rick McGuire > 27/04/2009 20:16 > > Please respond to > Open Object Rexx Developer Mailing List > > To > > Open Object Rexx Developer Mailing List > > cc > > Subject > > Re: [Oorexx-devel] Build 4507 -> 4521 > > Most of the commits in that range were to the branch where I tried > replacing the the C runtime functions with native ones. Add to that > the fact we're updating both the trunk and beta branch with all bug > fixes, the commit numbers ratchet up pretty quickly. > > However, it looks like the version that Mark provided for me also had > a patch I'd asked him to try out this morning, so that could have been > the source of the problem. > > Rick > > On Mon, Apr 27, 2009 at 3:10 PM, Mike Cowlishaw wrote: > > > >> The only other difference between 4507 and 4523 is the fix for > >> SysFileSearch(). Nothing at all related to rxapi. > > > > Sorry ... I meant Rexx APIs, not rxapi. > > > > I have exactly one call to SysFileSearch in all my Rexx programs, and > > definitely nowhere near the failing case (in fact I don't even remember > > writing that one, has not been run in year to two!). > > > > Any other changes from 4507->21 ? Sounds as though quite a lot of builds > > & changes? > > > > Mike > > > > > > > > > > > > Unless stated otherwise above: > > IBM United Kingdom Limited - Registered in England and Wales with number > > 741598. > > Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU > > > > > > > > > > > > > -- > > Crystal Reports - New Free Runtime and 30 Day Trial > > Check out the new simplified licensign option that enables unlimited > > royalty-free distribution of the report engine for externally facing > > server and web deployment. > > http://p.sf.net/sfu/businessobjects > > ___ > > Oorexx-devel mailing list > > Oorexx-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > > > -- > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensign option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU -- Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] ooRexx 4.0 Beta Refreshed (r4525), Now Available
The ooRexx 4.0 Beta files on SourceForge have been refreshed. The subversion level is 4525. All bugs reported during this beta, to date, have been fixed in this build. The files are available at: https://sourceforge.net/project/showfiles.php?group_id=119701 Those people participating in the beta and reporting bugs have had their bug(s) fixed. If you want *your* bug fixed before the official release, you need to test and report the bug now. Bugs reported after the public release of 4.0.0 will be fixed, but you won't see the fix until the next official release. The ooRexx Team -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Build 4507 -> 4521
Most of the commits in that range were to the branch where I tried replacing the the C runtime functions with native ones. Add to that the fact we're updating both the trunk and beta branch with all bug fixes, the commit numbers ratchet up pretty quickly. However, it looks like the version that Mark provided for me also had a patch I'd asked him to try out this morning, so that could have been the source of the problem. Rick On Mon, Apr 27, 2009 at 3:10 PM, Mike Cowlishaw wrote: > >> The only other difference between 4507 and 4523 is the fix for >> SysFileSearch(). Nothing at all related to rxapi. > > Sorry ... I meant Rexx APIs, not rxapi. > > I have exactly one call to SysFileSearch in all my Rexx programs, and > definitely nowhere near the failing case (in fact I don't even remember > writing that one, has not been run in year to two!). > > Any other changes from 4507->21 ? Sounds as though quite a lot of builds > & changes? > > Mike > > > > > > Unless stated otherwise above: > IBM United Kingdom Limited - Registered in England and Wales with number > 741598. > Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU > > > > > > -- > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensign option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Build 4507 -> 4521
> The only other difference between 4507 and 4523 is the fix for > SysFileSearch(). Nothing at all related to rxapi. Sorry ... I meant Rexx APIs, not rxapi. I have exactly one call to SysFileSearch in all my Rexx programs, and definitely nowhere near the failing case (in fact I don't even remember writing that one, has not been run in year to two!). Any other changes from 4507->21 ? Sounds as though quite a lot of builds & changes? Mike Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] I/O again
Rony G. Flatscher schrieb: > Here is another run, where this error occurs for the "exit" statement! > > Microsoft Windows XP [Version 5.1.2600] > (C) Copyright 1985-2001 Microsoft Corp. > > D:\Dokumente und Einstellungen\Administrator>rexxtry say hallo > HALLO > ... rexxtry.rex on WindowsNT > > D:\Dokumente und Einstellungen\Administrator>rexxtry > REXX-ooRexx_4.0.0(MT) 6.03 24 Apr 2009 > rexxtry.rex lets you interactively try REXX statements. > Each string is executed when you hit Enter. > Enter 'call tell' for a description of the features. > Go on - try a few...Enter 'exit' to end. > say sa > SA > ... rexxtry.rex on WindowsNT > > rexxtry.rex: Enter 'exit' to end. Or '?' for online REXX help. > exit > Der Befehl "RXIT" ist entweder falsch geschrieben oder > konnte nicht gefunden werden. > rc = 1 rexxtry.rex on WindowsNT This also occurrs for me. Not that I have any experience with C on Windows, but if it's needed I could still figure out how to setup the development environment. Moritz -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Build 4507 -> 4521
The only other difference between 4507 and 4523 is the fix for SysFileSearch(). Nothing at all related to rxapi. Rick On Mon, Apr 27, 2009 at 2:32 PM, Mike Cowlishaw wrote: > OK, here's update ... > >> I think Mike and I might have got crossed up by slow e-mails. >> (Maybe.) His subject title says 4521. But, the build with your fix >> in it was 4523. >> >> Anyhow, I pointed him to a 4523 build that is a fresh check out from >> the beta branch, rather than a build from my trunk. That way we can >> be sure exactly what the source is. > > I have now been running for about an hour with the 4523 build. > > It *does* look as though the 'r' overlay has gone! Break out the > Champagne! I was not able to recreate in Rexxtry or elap. Of course a > few more hours would be needed to be sure, but this does look good. > > However, the problem noted earlier -- a change between 4507 -> 4521 (i.e., > NOT due to the latest fix in 4523) is still there. Something to do with > the RxAPI? This has absolutely nothing to do with Parse Pull, as it is a > background web server task that writes to console but never reads from it. > > I'll try and get something specific in the morning, but at the moment all > I am getting is the Windows dialog about "app has failed and send data to > MS?". Meantime I have to back out to 4507 so I can get things finished > off for the day. > > Maybe a 4507 with the 'r'-killer fix would be the winner :-)) > > Mike > > > > > > > Unless stated otherwise above: > IBM United Kingdom Limited - Registered in England and Wales with number > 741598. > Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU > > > > > > > > -- > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensign option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Build 4507 -> 4521
OK, here's update ... > I think Mike and I might have got crossed up by slow e-mails. > (Maybe.) His subject title says 4521. But, the build with your fix > in it was 4523. > > Anyhow, I pointed him to a 4523 build that is a fresh check out from > the beta branch, rather than a build from my trunk. That way we can > be sure exactly what the source is. I have now been running for about an hour with the 4523 build. It *does* look as though the 'r' overlay has gone! Break out the Champagne! I was not able to recreate in Rexxtry or elap. Of course a few more hours would be needed to be sure, but this does look good. However, the problem noted earlier -- a change between 4507 -> 4521 (i.e., NOT due to the latest fix in 4523) is still there. Something to do with the RxAPI? This has absolutely nothing to do with Parse Pull, as it is a background web server task that writes to console but never reads from it. I'll try and get something specific in the morning, but at the moment all I am getting is the Windows dialog about "app has failed and send data to MS?". Meantime I have to back out to 4507 so I can get things finished off for the day. Maybe a 4507 with the 'r'-killer fix would be the winner :-)) Mike Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Build 4507 -> 4521
Rick, I think Mike and I might have got crossed up by slow e-mails. (Maybe.) His subject title says 4521. But, the build with your fix in it was 4523. Anyhow, I pointed him to a 4523 build that is a fresh check out from the beta branch, rather than a build from my trunk. That way we can be sure exactly what the source is. -- Mark Miesfeld On Mon, Apr 27, 2009 at 10:00 AM, Rick McGuire wrote: > This could conceivably be caused by the same change, but I'm probably > going to need something to recreate this so I can debug. > > Rick > > On Mon, Apr 27, 2009 at 12:55 PM, Mike Cowlishaw wrote: >> >> Something else changed between these builds ... now the first time GoServe >> calls Rexx it works fine, but on the second call it crashes with a C05 >> >> >> >> >> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - >> Mike Cowlishaw, IBM Fellow >> http://bit.ly/mfc >> IBM UK (MP8), PO Box 31, Birmingham Road, Warwick, CV34 5JL >> >> >> >> >> Unless stated otherwise above: >> IBM United Kingdom Limited - Registered in England and Wales with number >> 741598. >> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU >> >> >> >> >> >> -- >> Crystal Reports - New Free Runtime and 30 Day Trial >> Check out the new simplified licensign option that enables unlimited >> royalty-free distribution of the report engine for externally facing >> server and web deployment. >> http://p.sf.net/sfu/businessobjects >> ___ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> >> > > -- > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensign option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Build 4507 -> 4521
On Mon, Apr 27, 2009 at 9:55 AM, Mike Cowlishaw wrote: > Something else changed between these builds ... now the first time GoServe > calls Rexx it works fine, but on the second call it crashes with a C05 Mike, I did the build from trunk, rather than the beta source tree. Let me get you a build from the beta branch too be sure we are comparing apples to apples. I realize it might be too late for you to test it today, maybe tomorrow. -- Mark Miesfeld -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Build 4507 -> 4521
This could conceivably be caused by the same change, but I'm probably going to need something to recreate this so I can debug. Rick On Mon, Apr 27, 2009 at 12:55 PM, Mike Cowlishaw wrote: > > Something else changed between these builds ... now the first time GoServe > calls Rexx it works fine, but on the second call it crashes with a C05 > > > > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > Mike Cowlishaw, IBM Fellow > http://bit.ly/mfc > IBM UK (MP8), PO Box 31, Birmingham Road, Warwick, CV34 5JL > > > > > Unless stated otherwise above: > IBM United Kingdom Limited - Registered in England and Wales with number > 741598. > Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU > > > > > > -- > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensign option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Build 4507 -> 4521
Something else changed between these builds ... now the first time GoServe calls Rexx it works fine, but on the second call it crashes with a C05 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Mike Cowlishaw, IBM Fellow http://bit.ly/mfc IBM UK (MP8), PO Box 31, Birmingham Road, Warwick, CV34 5JL Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] I'll refresh the beta builds today
All, I'm planning on refreshing the beta builds on SourceForge today. All the bugs reported so far have been verified as fixed, except for Mike's of course. I'm hopeful that one is also. It seems there is a good chance of it. I know David is busy, so I'm planning on doing the Linux builds also. Rainer - don't feel pressured to do an AIX build. When you have time is fine. I'll add it to the files at that time. -- Mark Miesfeld -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] I/O again
It's fixed for me also. The new test build is almost ready, I'll let Mike know as soon as it is available. -- Mark Miesfeld On Mon, Apr 27, 2009 at 9:20 AM, Rick McGuire wrote: > I think I've fixed this! A big thanks to Rony...his method for > reproducing this was 100% effective once Mark gave me the key to > getting it to work. The problem only seemed to occur if our buffering > is turned off for stdin. When buffering was turned off, I would > consistently see the bogus character when _read() was called for the > first line. With buffering turned on, the _read() call would > generally retrieve up to the next complete line in one call and all of > the characters look good. Now comes the concrete test...seeing if this > works for Mike! > > Rick > > On Mon, Apr 27, 2009 at 11:28 AM, Rick McGuire wrote: >> This is useful. I now have a consistent means of reproducing this, >> I'm able to gather a little more debug info. Unfortunately, what I've >> gotten so far just confirms what I already new...that the bogus >> character is coming from the C runtime routine. >> >> RIck >> >> On Mon, Apr 27, 2009 at 11:17 AM, Mark Miesfeld wrote: >>> On Mon, Apr 27, 2009 at 8:09 AM, Rick McGuire wrote: >>> Ok, I've got the magic incantation correct now too. The key was not picking up the EOL for the exit command but physically hitting enter. I seem able to reproduce this reliably now too. >>> >>> That's good. I tried commenting out _setMode(fileHandle, _O_BINARY); >>> in setStdIn and it didn't seem to help. >>> >>> -- >>> Mark Miesfeld >>> >>> -- >>> Crystal Reports - New Free Runtime and 30 Day Trial >>> Check out the new simplified licensign option that enables unlimited >>> royalty-free distribution of the report engine for externally facing >>> server and web deployment. >>> http://p.sf.net/sfu/businessobjects >>> ___ >>> Oorexx-devel mailing list >>> Oorexx-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>> >> > > -- > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensign option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] I/O again
I saw your commit and am building from trunk right now. (Guess I should have built from the beta.) But, I think trunk is good enough for Mike to just try. -- Mark Miesfeld On Mon, Apr 27, 2009 at 9:20 AM, Rick McGuire wrote: > I think I've fixed this! A big thanks to Rony...his method for > reproducing this was 100% effective once Mark gave me the key to > getting it to work. The problem only seemed to occur if our buffering > is turned off for stdin. When buffering was turned off, I would > consistently see the bogus character when _read() was called for the > first line. With buffering turned on, the _read() call would > generally retrieve up to the next complete line in one call and all of > the characters look good. Now comes the concrete test...seeing if this > works for Mike! > > Rick > > On Mon, Apr 27, 2009 at 11:28 AM, Rick McGuire wrote: >> This is useful. I now have a consistent means of reproducing this, >> I'm able to gather a little more debug info. Unfortunately, what I've >> gotten so far just confirms what I already new...that the bogus >> character is coming from the C runtime routine. >> >> RIck >> >> On Mon, Apr 27, 2009 at 11:17 AM, Mark Miesfeld wrote: >>> On Mon, Apr 27, 2009 at 8:09 AM, Rick McGuire wrote: >>> Ok, I've got the magic incantation correct now too. The key was not picking up the EOL for the exit command but physically hitting enter. I seem able to reproduce this reliably now too. >>> >>> That's good. I tried commenting out _setMode(fileHandle, _O_BINARY); >>> in setStdIn and it didn't seem to help. >>> >>> -- >>> Mark Miesfeld >>> >>> -- >>> Crystal Reports - New Free Runtime and 30 Day Trial >>> Check out the new simplified licensign option that enables unlimited >>> royalty-free distribution of the report engine for externally facing >>> server and web deployment. >>> http://p.sf.net/sfu/businessobjects >>> ___ >>> Oorexx-devel mailing list >>> Oorexx-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>> >> > > -- > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensign option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] I/O again
I think I've fixed this! A big thanks to Rony...his method for reproducing this was 100% effective once Mark gave me the key to getting it to work. The problem only seemed to occur if our buffering is turned off for stdin. When buffering was turned off, I would consistently see the bogus character when _read() was called for the first line. With buffering turned on, the _read() call would generally retrieve up to the next complete line in one call and all of the characters look good. Now comes the concrete test...seeing if this works for Mike! Rick On Mon, Apr 27, 2009 at 11:28 AM, Rick McGuire wrote: > This is useful. I now have a consistent means of reproducing this, > I'm able to gather a little more debug info. Unfortunately, what I've > gotten so far just confirms what I already new...that the bogus > character is coming from the C runtime routine. > > RIck > > On Mon, Apr 27, 2009 at 11:17 AM, Mark Miesfeld wrote: >> On Mon, Apr 27, 2009 at 8:09 AM, Rick McGuire wrote: >> >>> Ok, I've got the magic incantation correct now too. The key was not >>> picking up the EOL for the exit command but physically hitting enter. >>> I seem able to reproduce this reliably now too. >> >> That's good. I tried commenting out _setMode(fileHandle, _O_BINARY); >> in setStdIn and it didn't seem to help. >> >> -- >> Mark Miesfeld >> >> -- >> Crystal Reports - New Free Runtime and 30 Day Trial >> Check out the new simplified licensign option that enables unlimited >> royalty-free distribution of the report engine for externally facing >> server and web deployment. >> http://p.sf.net/sfu/businessobjects >> ___ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> > -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] I/O again .. using Rexxtry
I hadn't thought of trying Rexxtry. Thanks Rony! An even simpler scenario: start Rexxtry, then just type a single letter command (and Enter) that is valid and does nothing (so returns very fast) (I have a c.rex that contains only a comment), and repeat, fast. Below is what I just got --- almost *every* 'c' command got converted to 'r' (which invokes r.rex -> remind.rex for me, which is invalid on its own hence the message).This seems to be much more repeatable than in my elap program. [Strangely .. then got in a mode where each empty command went very slow .. 0.5 seconds perhaps .. and did not fail. With some disk thrashing.] All this with today's build. Mike - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - c Remind needs a time (in minutes) rc = 0 .. rexxtry.rex on WindowsNT c rc = 0 .. rexxtry.rex on WindowsNT c Remind needs a time (in minutes) rc = 0 .. rexxtry.rex on WindowsNT c Remind needs a time (in minutes) rc = 0 .. rexxtry.rex on WindowsNT c Remind needs a time (in minutes) rc = 0 .. rexxtry.rex on WindowsNT c Remind needs a time (in minutes) rc = 0 .. rexxtry.rex on WindowsNT c Remind needs a time (in minutes) rc = 0 .. rexxtry.rex on WindowsNT c rc = 0 .. rexxtry.rex on WindowsNT c rc = 0 .. rexxtry.rex on WindowsNT c Remind needs a time (in minutes) rc = 0 .. rexxtry.rex on WindowsNT Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] I/O again
This is useful. I now have a consistent means of reproducing this, I'm able to gather a little more debug info. Unfortunately, what I've gotten so far just confirms what I already new...that the bogus character is coming from the C runtime routine. RIck On Mon, Apr 27, 2009 at 11:17 AM, Mark Miesfeld wrote: > On Mon, Apr 27, 2009 at 8:09 AM, Rick McGuire wrote: > >> Ok, I've got the magic incantation correct now too. The key was not >> picking up the EOL for the exit command but physically hitting enter. >> I seem able to reproduce this reliably now too. > > That's good. I tried commenting out _setMode(fileHandle, _O_BINARY); > in setStdIn and it didn't seem to help. > > -- > Mark Miesfeld > > -- > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensign option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] I/O again
On Mon, Apr 27, 2009 at 8:09 AM, Rick McGuire wrote: > Ok, I've got the magic incantation correct now too. The key was not > picking up the EOL for the exit command but physically hitting enter. > I seem able to reproduce this reliably now too. That's good. I tried commenting out _setMode(fileHandle, _O_BINARY); in setStdIn and it didn't seem to help. -- Mark Miesfeld -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] I/O again
> Okay, it's built. I sent Mike the link to get it. OK, will give it a try. Fingers-crossed ... Mike Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] I/O again
Ok, I've got the magic incantation correct now too. The key was not picking up the EOL for the exit command but physically hitting enter. I seem able to reproduce this reliably now too. Rick On Mon, Apr 27, 2009 at 11:05 AM, Mark Miesfeld wrote: > Okay, I'll try that. > > Tried with 3.2.0 about 10 times and it never happened. > > On 4.0.0, it happens for me every single time I paste the lines into > the console window. > > -- > Mark Miesfeld > > On Mon, Apr 27, 2009 at 8:01 AM, Rick McGuire wrote: >> Hmmm, this is starting to push the issue back to being an I/O problem. >> Here's something to try. In SysFile::setStdIn(), try commenting out >> the line >> >> _setMode(fileHandle, _O_BINARY); >> >> and see if you can recreate the problem. I'm wondering if switching >> the mode while characters are already in the buffer are causing this >> problem. This line was added because redirected input was causing >> problems. >> >> Rick >> >> >> On Mon, Apr 27, 2009 at 10:51 AM, Mark Miesfeld wrote: >>> I'm just about to try that. I was seeing how reliable it was that I >>> saw RXIT. Seems to be ever time when I paste the text into the >>> window. >>> >>> I think another key is that Rony says he sees it when: >>> immediately issuing a say statement (typing while rexxtry.rex starts up). >>> >>> So here, the keyboard buffer has data in it (probably, depending on >>> fast he is typing) when the interpreter starts. >>> >>> I'll post as soon as I try it with the patched version. >>> >>> -- >>> Mark Miesfeld. >>> >>> On Mon, Apr 27, 2009 at 7:47 AM, Rick McGuire wrote: Have you tried reproducing using the patched version? I tried this technique this morning both the unpatched and official beta version and didn't get any failures. Rick On Mon, Apr 27, 2009 at 10:42 AM, Mark Miesfeld wrote: > Well, okay. By pasting lines into a console window, I got RXIT: > > D:\Interpreters\Rexx>rexx -v > Open Object Rexx Version 4.0.0 > Build date: Apr 20 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 > D:\Interpreters\Rexx>rexxtry say hallo > HALLO > ... rexxtry.rex on WindowsNT > > D:\Interpreters\Rexx>rexxtry > REXX-ooRexx_4.0.0(MT) 6.03 20 Apr 2009 > rexxtry.rex lets you interactively try REXX statements. > Each string is executed when you hit Enter. > Enter 'call tell' for a description of the features. > Go on - try a few... Enter 'exit' to end. > say sa > SA > ... rexxtry.rex on WindowsNT > > rexxtry.rex: Enter 'exit' to end. Or '?' for online REXX help. > exit > 'RXIT' is not recognized as an internal or external command, > operable program or batch file. > rc = 1 rexxtry.rex on WindowsNT > > > Prior to that I tried typing the lines in the console window and had > no luck. When I pasted the lines it was the same console window I had > been using before. > > In the pasting case, the keyboard buffer would have data in it when > the second interpreter started. > > -- > Mark Miesfeld > > > On Mon, Apr 27, 2009 at 6:17 AM, Rony G. Flatscher > wrote: >> Pretty regularly I can get that problem too when opening a command line >> window, and first thing I would do is using rexxtry and immediately >> issuing >> a say statement (typing while rexxtry.rex starts up). Here's an example >> that >> works *quite reliably* for me: >> >> Microsoft Windows XP [Version 5.1.2600] >> (C) Copyright 1985-2001 Microsoft Corp. >> D:\Dokumente und Einstellungen\Administrator>rexxtry say hallo >> HALLO >> ... rexxtry.rex on WindowsNT >> D:\Dokumente und Einstellungen\Administrator>rexxtry >> REXX-ooRexx_4.0.0(MT) 6.03 24 Apr 2009 >> rexxtry.rex lets you interactively try REXX statements. >> Each string is executed when you hit Enter. >> Enter 'call tell' for a description of the features. >> Go on - try a few... Enter 'exit' to end. >> say sa >> Der Befehl "RAY" ist entweder falsch geschrieben oder >> konnte nicht gefunden werden. >> rc = 1 rexxtry.rex on WindowsNT >> >> >> Here is what maybe work for you: >> >> First copy the following lines into the clipboard (note there is a >> trailing >> blank line): >> >> rexxtry say hallo >> rexxtry >> say sa >> >> e
Re: [Oorexx-devel] I/O again
Okay, I'll try that. Tried with 3.2.0 about 10 times and it never happened. On 4.0.0, it happens for me every single time I paste the lines into the console window. -- Mark Miesfeld On Mon, Apr 27, 2009 at 8:01 AM, Rick McGuire wrote: > Hmmm, this is starting to push the issue back to being an I/O problem. > Here's something to try. In SysFile::setStdIn(), try commenting out > the line > > _setMode(fileHandle, _O_BINARY); > > and see if you can recreate the problem. I'm wondering if switching > the mode while characters are already in the buffer are causing this > problem. This line was added because redirected input was causing > problems. > > Rick > > > On Mon, Apr 27, 2009 at 10:51 AM, Mark Miesfeld wrote: >> I'm just about to try that. I was seeing how reliable it was that I >> saw RXIT. Seems to be ever time when I paste the text into the >> window. >> >> I think another key is that Rony says he sees it when: >> >>> immediately issuing a say statement (typing while rexxtry.rex starts up). >> >> So here, the keyboard buffer has data in it (probably, depending on >> fast he is typing) when the interpreter starts. >> >> I'll post as soon as I try it with the patched version. >> >> -- >> Mark Miesfeld. >> >> On Mon, Apr 27, 2009 at 7:47 AM, Rick McGuire wrote: >>> Have you tried reproducing using the patched version? I tried this >>> technique this morning both the unpatched and official beta version >>> and didn't get any failures. >>> >>> Rick >>> >>> On Mon, Apr 27, 2009 at 10:42 AM, Mark Miesfeld wrote: Well, okay. By pasting lines into a console window, I got RXIT: D:\Interpreters\Rexx>rexx -v Open Object Rexx Version 4.0.0 Build date: Apr 20 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 D:\Interpreters\Rexx>rexxtry say hallo HALLO ... rexxtry.rex on WindowsNT D:\Interpreters\Rexx>rexxtry REXX-ooRexx_4.0.0(MT) 6.03 20 Apr 2009 rexxtry.rex lets you interactively try REXX statements. Each string is executed when you hit Enter. Enter 'call tell' for a description of the features. Go on - try a few... Enter 'exit' to end. say sa SA ... rexxtry.rex on WindowsNT rexxtry.rex: Enter 'exit' to end. Or '?' for online REXX help. exit 'RXIT' is not recognized as an internal or external command, operable program or batch file. rc = 1 rexxtry.rex on WindowsNT Prior to that I tried typing the lines in the console window and had no luck. When I pasted the lines it was the same console window I had been using before. In the pasting case, the keyboard buffer would have data in it when the second interpreter started. -- Mark Miesfeld On Mon, Apr 27, 2009 at 6:17 AM, Rony G. Flatscher wrote: > Pretty regularly I can get that problem too when opening a command line > window, and first thing I would do is using rexxtry and immediately > issuing > a say statement (typing while rexxtry.rex starts up). Here's an example > that > works *quite reliably* for me: > > Microsoft Windows XP [Version 5.1.2600] > (C) Copyright 1985-2001 Microsoft Corp. > D:\Dokumente und Einstellungen\Administrator>rexxtry say hallo > HALLO > ... rexxtry.rex on WindowsNT > D:\Dokumente und Einstellungen\Administrator>rexxtry > REXX-ooRexx_4.0.0(MT) 6.03 24 Apr 2009 > rexxtry.rex lets you interactively try REXX statements. > Each string is executed when you hit Enter. > Enter 'call tell' for a description of the features. > Go on - try a few... Enter 'exit' to end. > say sa > Der Befehl "RAY" ist entweder falsch geschrieben oder > konnte nicht gefunden werden. > rc = 1 rexxtry.rex on WindowsNT > > > Here is what maybe work for you: > > First copy the following lines into the clipboard (note there is a > trailing > blank line): > > rexxtry say hallo > rexxtry > say sa > > exit > > Make sure no Rexx program runs, and no command line window is open in > which > a Rexx program ran (not sure whether that is really necessary, but who > knows) > Open a new command line window > Just paste the above lines into the window; if necessary repeat steps 2 > through 4 > > Eventually (within ten attempts) the error comes up again
Re: [Oorexx-devel] I/O again
On Mon, Apr 27, 2009 at 7:47 AM, Rick McGuire wrote: > Have you tried reproducing using the patched version? I tried this > technique this morning both the unpatched and official beta version > and didn't get any failures. Yes, I just tried with the patched build I did earlier this morning and get the same RXIT: E:\>rexx -v Open Object Rexx Version 4.0.0 Build date: Apr 27 2009 Addressing Mode: 32 E:\>rexxtry say hallo HALLO ... rexxtry.rex on WindowsNT E:\>rexxtry REXX-ooRexx_4.0.0(MT) 6.03 27 Apr 2009 rexxtry.rex lets you interactively try REXX statements. Each string is executed when you hit Enter. Enter 'call tell' for a description of the features. Go on - try a few...Enter 'exit' to end. say sa SA ... rexxtry.rex on WindowsNT rexxtry.rex: Enter 'exit' to end. Or '?' for online REXX help. exit 'RXIT' is not recognized as an internal or external command, operable program or batch file. rc = 1 rexxtry.rex on WindowsNT When I paste the text in, everything runs and ends up on the line with exit already on it. When I then hit ENTER, I get the RXIT. I just tried not hitting ENTER, but instead using the arrow key to move to the start of the line and retype 'exit' I still get the RXIT. I haven't tried this 'pasting' think on 3.2.0. Going to do that next. -- Mark Miesfeld -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] I/O again
Hmmm, this is starting to push the issue back to being an I/O problem. Here's something to try. In SysFile::setStdIn(), try commenting out the line _setMode(fileHandle, _O_BINARY); and see if you can recreate the problem. I'm wondering if switching the mode while characters are already in the buffer are causing this problem. This line was added because redirected input was causing problems. Rick On Mon, Apr 27, 2009 at 10:51 AM, Mark Miesfeld wrote: > I'm just about to try that. I was seeing how reliable it was that I > saw RXIT. Seems to be ever time when I paste the text into the > window. > > I think another key is that Rony says he sees it when: > >> immediately issuing a say statement (typing while rexxtry.rex starts up). > > So here, the keyboard buffer has data in it (probably, depending on > fast he is typing) when the interpreter starts. > > I'll post as soon as I try it with the patched version. > > -- > Mark Miesfeld. > > On Mon, Apr 27, 2009 at 7:47 AM, Rick McGuire wrote: >> Have you tried reproducing using the patched version? I tried this >> technique this morning both the unpatched and official beta version >> and didn't get any failures. >> >> Rick >> >> On Mon, Apr 27, 2009 at 10:42 AM, Mark Miesfeld wrote: >>> Well, okay. By pasting lines into a console window, I got RXIT: >>> >>> D:\Interpreters\Rexx>rexx -v >>> Open Object Rexx Version 4.0.0 >>> Build date: Apr 20 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 >>> D:\Interpreters\Rexx>rexxtry say hallo >>> HALLO >>> ... rexxtry.rex on WindowsNT >>> >>> D:\Interpreters\Rexx>rexxtry >>> REXX-ooRexx_4.0.0(MT) 6.03 20 Apr 2009 >>> rexxtry.rex lets you interactively try REXX statements. >>> Each string is executed when you hit Enter. >>> Enter 'call tell' for a description of the features. >>> Go on - try a few... Enter 'exit' to end. >>> say sa >>> SA >>> ... rexxtry.rex on WindowsNT >>> >>> rexxtry.rex: Enter 'exit' to end. Or '?' for online REXX help. >>> exit >>> 'RXIT' is not recognized as an internal or external command, >>> operable program or batch file. >>> rc = 1 rexxtry.rex on WindowsNT >>> >>> >>> Prior to that I tried typing the lines in the console window and had >>> no luck. When I pasted the lines it was the same console window I had >>> been using before. >>> >>> In the pasting case, the keyboard buffer would have data in it when >>> the second interpreter started. >>> >>> -- >>> Mark Miesfeld >>> >>> >>> On Mon, Apr 27, 2009 at 6:17 AM, Rony G. Flatscher >>> wrote: Pretty regularly I can get that problem too when opening a command line window, and first thing I would do is using rexxtry and immediately issuing a say statement (typing while rexxtry.rex starts up). Here's an example that works *quite reliably* for me: Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. D:\Dokumente und Einstellungen\Administrator>rexxtry say hallo HALLO ... rexxtry.rex on WindowsNT D:\Dokumente und Einstellungen\Administrator>rexxtry REXX-ooRexx_4.0.0(MT) 6.03 24 Apr 2009 rexxtry.rex lets you interactively try REXX statements. Each string is executed when you hit Enter. Enter 'call tell' for a description of the features. Go on - try a few... Enter 'exit' to end. say sa Der Befehl "RAY" ist entweder falsch geschrieben oder konnte nicht gefunden werden. rc = 1 rexxtry.rex on WindowsNT Here is what maybe work for you: First copy the following lines into the clipboard (note there is a trailing blank line): rexxtry say hallo rexxtry say sa exit Make sure no Rexx program runs, and no command line window is open in which a Rexx program ran (not sure whether that is really necessary, but who knows) Open a new command line window Just paste the above lines into the window; if necessary repeat steps 2 through 4 Eventually (within ten attempts) the error comes up again (although I might have waited in between invocations, after having all command line windows closed). Here is another run, where this error occurs for the "exit" statement! Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. D:\Dokumente und Einstellungen\Administrator>rexxtry say hallo HALLO .
Re: [Oorexx-devel] I/O again
I'm just about to try that. I was seeing how reliable it was that I saw RXIT. Seems to be ever time when I paste the text into the window. I think another key is that Rony says he sees it when: > immediately issuing a say statement (typing while rexxtry.rex starts up). So here, the keyboard buffer has data in it (probably, depending on fast he is typing) when the interpreter starts. I'll post as soon as I try it with the patched version. -- Mark Miesfeld. On Mon, Apr 27, 2009 at 7:47 AM, Rick McGuire wrote: > Have you tried reproducing using the patched version? I tried this > technique this morning both the unpatched and official beta version > and didn't get any failures. > > Rick > > On Mon, Apr 27, 2009 at 10:42 AM, Mark Miesfeld wrote: >> Well, okay. By pasting lines into a console window, I got RXIT: >> >> D:\Interpreters\Rexx>rexx -v >> Open Object Rexx Version 4.0.0 >> Build date: Apr 20 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 >> D:\Interpreters\Rexx>rexxtry say hallo >> HALLO >> ... rexxtry.rex on WindowsNT >> >> D:\Interpreters\Rexx>rexxtry >> REXX-ooRexx_4.0.0(MT) 6.03 20 Apr 2009 >> rexxtry.rex lets you interactively try REXX statements. >> Each string is executed when you hit Enter. >> Enter 'call tell' for a description of the features. >> Go on - try a few... Enter 'exit' to end. >> say sa >> SA >> ... rexxtry.rex on WindowsNT >> >> rexxtry.rex: Enter 'exit' to end. Or '?' for online REXX help. >> exit >> 'RXIT' is not recognized as an internal or external command, >> operable program or batch file. >> rc = 1 rexxtry.rex on WindowsNT >> >> >> Prior to that I tried typing the lines in the console window and had >> no luck. When I pasted the lines it was the same console window I had >> been using before. >> >> In the pasting case, the keyboard buffer would have data in it when >> the second interpreter started. >> >> -- >> Mark Miesfeld >> >> >> On Mon, Apr 27, 2009 at 6:17 AM, Rony G. Flatscher >> wrote: >>> Pretty regularly I can get that problem too when opening a command line >>> window, and first thing I would do is using rexxtry and immediately issuing >>> a say statement (typing while rexxtry.rex starts up). Here's an example that >>> works *quite reliably* for me: >>> >>> Microsoft Windows XP [Version 5.1.2600] >>> (C) Copyright 1985-2001 Microsoft Corp. >>> D:\Dokumente und Einstellungen\Administrator>rexxtry say hallo >>> HALLO >>> ... rexxtry.rex on WindowsNT >>> D:\Dokumente und Einstellungen\Administrator>rexxtry >>> REXX-ooRexx_4.0.0(MT) 6.03 24 Apr 2009 >>> rexxtry.rex lets you interactively try REXX statements. >>> Each string is executed when you hit Enter. >>> Enter 'call tell' for a description of the features. >>> Go on - try a few... Enter 'exit' to end. >>> say sa >>> Der Befehl "RAY" ist entweder falsch geschrieben oder >>> konnte nicht gefunden werden. >>> rc = 1 rexxtry.rex on WindowsNT >>> >>> >>> Here is what maybe work for you: >>> >>> First copy the following lines into the clipboard (note there is a trailing >>> blank line): >>> >>> rexxtry say hallo >>> rexxtry >>> say sa >>> >>> exit >>> >>> Make sure no Rexx program runs, and no command line window is open in which >>> a Rexx program ran (not sure whether that is really necessary, but who >>> knows) >>> Open a new command line window >>> Just paste the above lines into the window; if necessary repeat steps 2 >>> through 4 >>> >>> Eventually (within ten attempts) the error comes up again (although I might >>> have waited in between invocations, after having all command line windows >>> closed). >>> >>> >>> Here is another run, where this error occurs for the "exit" statement! >>> >>> Microsoft Windows XP [Version 5.1.2600] >>> (C) Copyright 1985-2001 Microsoft Corp. >>> D:\Dokumente und Einstellungen\Administrator>rexxtry say hallo >>> HALLO >>> ... rexxtry.rex on WindowsNT >>> D:\Dokumente und Einstellungen\Administrator>rexxtry >>> REXX-ooRexx_4.0.0(MT) 6.03 24 Apr 2009 >>> rexxtry.rex lets you interactively try REXX statements. >>> Each string is executed when you hit Enter. >>> Enter 'call tell' for a description of the features. >>> Go on - try a few... Enter 'exit' to end. >>> say sa >>> SA >>> ... rexxtry.rex on WindowsNT >>> rexxtry.rex: Enter 'exit' to end. Or '?' for online REXX help. >>> exit >>> Der Befehl "RXIT" ist entweder falsch geschr
Re: [Oorexx-devel] I/O again
Have you tried reproducing using the patched version? I tried this technique this morning both the unpatched and official beta version and didn't get any failures. Rick On Mon, Apr 27, 2009 at 10:42 AM, Mark Miesfeld wrote: > Well, okay. By pasting lines into a console window, I got RXIT: > > D:\Interpreters\Rexx>rexx -v > Open Object Rexx Version 4.0.0 > Build date: Apr 20 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 > D:\Interpreters\Rexx>rexxtry say hallo > HALLO > ... rexxtry.rex on WindowsNT > > D:\Interpreters\Rexx>rexxtry > REXX-ooRexx_4.0.0(MT) 6.03 20 Apr 2009 > rexxtry.rex lets you interactively try REXX statements. > Each string is executed when you hit Enter. > Enter 'call tell' for a description of the features. > Go on - try a few... Enter 'exit' to end. > say sa > SA > ... rexxtry.rex on WindowsNT > > rexxtry.rex: Enter 'exit' to end. Or '?' for online REXX help. > exit > 'RXIT' is not recognized as an internal or external command, > operable program or batch file. > rc = 1 rexxtry.rex on WindowsNT > > > Prior to that I tried typing the lines in the console window and had > no luck. When I pasted the lines it was the same console window I had > been using before. > > In the pasting case, the keyboard buffer would have data in it when > the second interpreter started. > > -- > Mark Miesfeld > > > On Mon, Apr 27, 2009 at 6:17 AM, Rony G. Flatscher > wrote: >> Pretty regularly I can get that problem too when opening a command line >> window, and first thing I would do is using rexxtry and immediately issuing >> a say statement (typing while rexxtry.rex starts up). Here's an example that >> works *quite reliably* for me: >> >> Microsoft Windows XP [Version 5.1.2600] >> (C) Copyright 1985-2001 Microsoft Corp. >> D:\Dokumente und Einstellungen\Administrator>rexxtry say hallo >> HALLO >> ... rexxtry.rex on WindowsNT >> D:\Dokumente und Einstellungen\Administrator>rexxtry >> REXX-ooRexx_4.0.0(MT) 6.03 24 Apr 2009 >> rexxtry.rex lets you interactively try REXX statements. >> Each string is executed when you hit Enter. >> Enter 'call tell' for a description of the features. >> Go on - try a few... Enter 'exit' to end. >> say sa >> Der Befehl "RAY" ist entweder falsch geschrieben oder >> konnte nicht gefunden werden. >> rc = 1 rexxtry.rex on WindowsNT >> >> >> Here is what maybe work for you: >> >> First copy the following lines into the clipboard (note there is a trailing >> blank line): >> >> rexxtry say hallo >> rexxtry >> say sa >> >> exit >> >> Make sure no Rexx program runs, and no command line window is open in which >> a Rexx program ran (not sure whether that is really necessary, but who >> knows) >> Open a new command line window >> Just paste the above lines into the window; if necessary repeat steps 2 >> through 4 >> >> Eventually (within ten attempts) the error comes up again (although I might >> have waited in between invocations, after having all command line windows >> closed). >> >> >> Here is another run, where this error occurs for the "exit" statement! >> >> Microsoft Windows XP [Version 5.1.2600] >> (C) Copyright 1985-2001 Microsoft Corp. >> D:\Dokumente und Einstellungen\Administrator>rexxtry say hallo >> HALLO >> ... rexxtry.rex on WindowsNT >> D:\Dokumente und Einstellungen\Administrator>rexxtry >> REXX-ooRexx_4.0.0(MT) 6.03 24 Apr 2009 >> rexxtry.rex lets you interactively try REXX statements. >> Each string is executed when you hit Enter. >> Enter 'call tell' for a description of the features. >> Go on - try a few... Enter 'exit' to end. >> say sa >> SA >> ... rexxtry.rex on WindowsNT >> rexxtry.rex: Enter 'exit' to end. Or '?' for online REXX help. >> exit >> Der Befehl "RXIT" ist entweder falsch geschrieben oder >> konnte nicht gefunden werden. >> rc = 1 rexxtry.rex on WindowsNT >> >> >> HTH, >> >> ---rony >> >> >> -- >> Crystal Reports - New Free Runtime and 30 Day Trial >> Check out the new simplified licensign option that enables unlimited >> royalty-free distribution of the report engine for externally facing >> server and web deployment. >> http://p.sf.net/sfu/businessobjects >> ___ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> https://lists.sourcefor
Re: [Oorexx-devel] I/O again
Well, okay. By pasting lines into a console window, I got RXIT: D:\Interpreters\Rexx>rexx -v Open Object Rexx Version 4.0.0 Build date: Apr 20 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 D:\Interpreters\Rexx>rexxtry say hallo HALLO ... rexxtry.rex on WindowsNT D:\Interpreters\Rexx>rexxtry REXX-ooRexx_4.0.0(MT) 6.03 20 Apr 2009 rexxtry.rex lets you interactively try REXX statements. Each string is executed when you hit Enter. Enter 'call tell' for a description of the features. Go on - try a few...Enter 'exit' to end. say sa SA ... rexxtry.rex on WindowsNT rexxtry.rex: Enter 'exit' to end. Or '?' for online REXX help. exit 'RXIT' is not recognized as an internal or external command, operable program or batch file. rc = 1 rexxtry.rex on WindowsNT Prior to that I tried typing the lines in the console window and had no luck. When I pasted the lines it was the same console window I had been using before. In the pasting case, the keyboard buffer would have data in it when the second interpreter started. -- Mark Miesfeld On Mon, Apr 27, 2009 at 6:17 AM, Rony G. Flatscher wrote: > Pretty regularly I can get that problem too when opening a command line > window, and first thing I would do is using rexxtry and immediately issuing > a say statement (typing while rexxtry.rex starts up). Here's an example that > works *quite reliably* for me: > > Microsoft Windows XP [Version 5.1.2600] > (C) Copyright 1985-2001 Microsoft Corp. > D:\Dokumente und Einstellungen\Administrator>rexxtry say hallo > HALLO > ... rexxtry.rex on WindowsNT > D:\Dokumente und Einstellungen\Administrator>rexxtry > REXX-ooRexx_4.0.0(MT) 6.03 24 Apr 2009 > rexxtry.rex lets you interactively try REXX statements. > Each string is executed when you hit Enter. > Enter 'call tell' for a description of the features. > Go on - try a few...Enter 'exit' to end. > say sa > Der Befehl "RAY" ist entweder falsch geschrieben oder > konnte nicht gefunden werden. > rc = 1 rexxtry.rex on WindowsNT > > > Here is what maybe work for you: > > First copy the following lines into the clipboard (note there is a trailing > blank line): > > rexxtry say hallo > rexxtry > say sa > > exit > > Make sure no Rexx program runs, and no command line window is open in which > a Rexx program ran (not sure whether that is really necessary, but who > knows) > Open a new command line window > Just paste the above lines into the window; if necessary repeat steps 2 > through 4 > > Eventually (within ten attempts) the error comes up again (although I might > have waited in between invocations, after having all command line windows > closed). > > > Here is another run, where this error occurs for the "exit" statement! > > Microsoft Windows XP [Version 5.1.2600] > (C) Copyright 1985-2001 Microsoft Corp. > D:\Dokumente und Einstellungen\Administrator>rexxtry say hallo > HALLO > ... rexxtry.rex on WindowsNT > D:\Dokumente und Einstellungen\Administrator>rexxtry > REXX-ooRexx_4.0.0(MT) 6.03 24 Apr 2009 > rexxtry.rex lets you interactively try REXX statements. > Each string is executed when you hit Enter. > Enter 'call tell' for a description of the features. > Go on - try a few...Enter 'exit' to end. > say sa > SA > ... rexxtry.rex on WindowsNT > rexxtry.rex: Enter 'exit' to end. Or '?' for online REXX help. > exit > Der Befehl "RXIT" ist entweder falsch geschrieben oder > konnte nicht gefunden werden. > rc = 1 rexxtry.rex on WindowsNT > > > HTH, > > ---rony > > > -- > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensign option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects
Re: [Oorexx-devel] I/O again
Pretty regularly I can get that problem too when opening a command line window, and first thing I would do is using rexxtry and immediately issuing a say statement (typing while rexxtry.rex starts up). Here's an example that works *quite reliably* for me: Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. D:\Dokumente und Einstellungen\Administrator>rexxtry say hallo HALLO ... rexxtry.rex on WindowsNT D:\Dokumente und Einstellungen\Administrator>rexxtry REXX-ooRexx_4.0.0(MT) 6.03 24 Apr 2009 rexxtry.rex lets you interactively try REXX statements. Each string is executed when you hit Enter. Enter 'call tell' for a description of the features. Go on - try a few...Enter 'exit' to end. say sa Der Befehl "RAY" ist entweder falsch geschrieben oder konnte nicht gefunden werden. rc = 1 rexxtry.rex on WindowsNT Here is what maybe work for you: 1. First copy the following lines into the clipboard (note there is a trailing blank line): rexxtry say hallo rexxtry say sa exit 2. Make sure no Rexx program runs, and no command line window is open in which a Rexx program ran (not sure whether that is really necessary, but who knows) 3. Open a new command line window 4. Just paste the above lines into the window; if necessary repeat steps 2 through 4 Eventually (within ten attempts) the error comes up again (although I might have waited in between invocations, after having all command line windows closed). Here is another run, where this error occurs for the "exit" statement! Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. D:\Dokumente und Einstellungen\Administrator>rexxtry say hallo HALLO ... rexxtry.rex on WindowsNT D:\Dokumente und Einstellungen\Administrator>rexxtry REXX-ooRexx_4.0.0(MT) 6.03 24 Apr 2009 rexxtry.rex lets you interactively try REXX statements. Each string is executed when you hit Enter. Enter 'call tell' for a description of the features. Go on - try a few...Enter 'exit' to end. say sa SA ... rexxtry.rex on WindowsNT rexxtry.rex: Enter 'exit' to end. Or '?' for online REXX help. exit Der Befehl "RXIT" ist entweder falsch geschrieben oder konnte nicht gefunden werden. rc = 1 rexxtry.rex on WindowsNT HTH, ---rony -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] I/O again
Okay, it's built. I sent Mike the link to get it. -- Mark Miesfeld On Mon, Apr 27, 2009 at 5:48 AM, Mark Miesfeld wrote: > I've applied the patch and am building the install package right now. > I'll let you know when it's ready Mike. > > Rick, I'm hopeful about this. On Windows I really think we should > only use GlobalAlloc and its relatives instead of malloc. The only > time I use malloc is when I'm going to free it right there within the > same function. > > -- > Mark Miesfeld > > On Mon, Apr 27, 2009 at 4:40 AM, Rick McGuire wrote: >> Ok, I have one more thing to try. I'm starting to think this might be >> a memory-management issue, not an I/O issue. The buffer used for the >> I/O is one of the few places in the ooRexx code where malloc() is used >> to allocate memory. In fact, it wouldn't surprise me if this is the >> first malloc request done by the interpreter. I'm starting to wonder >> if the overlay might be related to some sort of activity taking place >> to manage the .exe program in the window, and there is some sort of >> race condition that occurs with that memory when enter is pressed. >> I've sent Mark a patch that changes the mechanism used to allocate >> this buffer and we'll give it one more try. If this fails, then I'm >> am totally out of ideas. We're running out of things to try changing. >> >> Rick >> >> On Mon, Apr 27, 2009 at 4:33 AM, Mike Cowlishaw wrote: >>> >>> Sorry to report that the dreaded 'r' still appears with Rick's latest (build >>> 4507). >>> >>> >>> >>> Maybe best to just document this in the readme as a probable Windows >>> problem? >>> >>> Everything else is working beautifully! >>> >>> Mike >>> >>> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - >>> Mike Cowlishaw, IBM Fellow >>> http://bit.ly/mfc >>> IBM UK (MP8), PO Box 31, Birmingham Road, Warwick, CV34 5JL >>> >>> >>> >>> >>> Unless stated otherwise above: >>> IBM United Kingdom Limited - Registered in England and Wales with number >>> 741598. >>> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU >>> >>> >>> >>> >>> >>> -- >>> Crystal Reports - New Free Runtime and 30 Day Trial >>> Check out the new simplified licensign option that enables unlimited >>> royalty-free distribution of the report engine for externally facing >>> server and web deployment. >>> http://p.sf.net/sfu/businessobjects >>> ___ >>> Oorexx-devel mailing list >>> Oorexx-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>> >>> >> >> -- >> Crystal Reports - New Free Runtime and 30 Day Trial >> Check out the new simplified licensign option that enables unlimited >> royalty-free distribution of the report engine for externally facing >> server and web deployment. >> http://p.sf.net/sfu/businessobjects >> ___ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> > -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] I/O again
I've applied the patch and am building the install package right now. I'll let you know when it's ready Mike. Rick, I'm hopeful about this. On Windows I really think we should only use GlobalAlloc and its relatives instead of malloc. The only time I use malloc is when I'm going to free it right there within the same function. -- Mark Miesfeld On Mon, Apr 27, 2009 at 4:40 AM, Rick McGuire wrote: > Ok, I have one more thing to try. I'm starting to think this might be > a memory-management issue, not an I/O issue. The buffer used for the > I/O is one of the few places in the ooRexx code where malloc() is used > to allocate memory. In fact, it wouldn't surprise me if this is the > first malloc request done by the interpreter. I'm starting to wonder > if the overlay might be related to some sort of activity taking place > to manage the .exe program in the window, and there is some sort of > race condition that occurs with that memory when enter is pressed. > I've sent Mark a patch that changes the mechanism used to allocate > this buffer and we'll give it one more try. If this fails, then I'm > am totally out of ideas. We're running out of things to try changing. > > Rick > > On Mon, Apr 27, 2009 at 4:33 AM, Mike Cowlishaw wrote: >> >> Sorry to report that the dreaded 'r' still appears with Rick's latest (build >> 4507). >> >> >> >> Maybe best to just document this in the readme as a probable Windows >> problem? >> >> Everything else is working beautifully! >> >> Mike >> >> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - >> Mike Cowlishaw, IBM Fellow >> http://bit.ly/mfc >> IBM UK (MP8), PO Box 31, Birmingham Road, Warwick, CV34 5JL >> >> >> >> >> Unless stated otherwise above: >> IBM United Kingdom Limited - Registered in England and Wales with number >> 741598. >> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU >> >> >> >> >> >> -- >> Crystal Reports - New Free Runtime and 30 Day Trial >> Check out the new simplified licensign option that enables unlimited >> royalty-free distribution of the report engine for externally facing >> server and web deployment. >> http://p.sf.net/sfu/businessobjects >> ___ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> >> > > -- > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensign option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] I/O again
Ok, I have one more thing to try. I'm starting to think this might be a memory-management issue, not an I/O issue. The buffer used for the I/O is one of the few places in the ooRexx code where malloc() is used to allocate memory. In fact, it wouldn't surprise me if this is the first malloc request done by the interpreter. I'm starting to wonder if the overlay might be related to some sort of activity taking place to manage the .exe program in the window, and there is some sort of race condition that occurs with that memory when enter is pressed. I've sent Mark a patch that changes the mechanism used to allocate this buffer and we'll give it one more try. If this fails, then I'm am totally out of ideas. We're running out of things to try changing. Rick On Mon, Apr 27, 2009 at 4:33 AM, Mike Cowlishaw wrote: > > Sorry to report that the dreaded 'r' still appears with Rick's latest (build > 4507). > > > > Maybe best to just document this in the readme as a probable Windows > problem? > > Everything else is working beautifully! > > Mike > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > Mike Cowlishaw, IBM Fellow > http://bit.ly/mfc > IBM UK (MP8), PO Box 31, Birmingham Road, Warwick, CV34 5JL > > > > > Unless stated otherwise above: > IBM United Kingdom Limited - Registered in England and Wales with number > 741598. > Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU > > > > > > -- > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensign option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] I/O again
Sorry to report that the dreaded 'r' still appears with Rick's latest (build 4507). Maybe best to just document this in the readme as a probable Windows problem? Everything else is working beautifully! Mike - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Mike Cowlishaw, IBM Fellow http://bit.ly/mfc IBM UK (MP8), PO Box 31, Birmingham Road, Warwick, CV34 5JL Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
