Rick,
Please include compiled dlls with this. I don't have the appropriate
Java SDK to installed on my machine to compile this.
O.K. here is the link to them:
http://wi.wu-wien.ac.at/rgf/rexx/misc/bugs/.
The CRASH-zip archives contain the respective versions of the DLL,
compiled for
93 is really the more correct error, so I think that behavior should stay.
Rick
On Mon, May 4, 2009 at 11:06 PM, Mark Miesfeld miesf...@gmail.com wrote:
Rick,
This test:
self~expectSyntax(40.0)
ret = stream(fileName, 'C', open read append)
self~assertSame(READY:, ret)
passes under 3.2.0
Rick McGuire wrote:
I'm not seeing a crash with either version of this dll.
That's strange!
In the zip-archives I have enclosed also the hs_err_pid*.log files
that the JVM creates.
This is using:
* Windows XP, SP 3
* Sun's Java 1.4 (but also occurred on later versions, will retest
None of which is of any value to me for debugging this problem. I'm
not getting any crashes, and the output printed to the screen is
exactly what I would expect from looking at the code.
Rick
On Tue, May 5, 2009 at 6:36 AM, Rony G. Flatscher
rony.flatsc...@wu-wien.ac.at wrote:
Rick McGuire
Ok, I was able to reproduce this using the NODEBUG version and I think
I have a fix.
Rick
On Tue, May 5, 2009 at 6:36 AM, Rony G. Flatscher
rony.flatsc...@wu-wien.ac.at wrote:
Rick McGuire wrote:
I'm not seeing a crash with either version of this dll.
That's strange!
In the zip-archives
http://msdn.microsoft.com/en-us/library/wztycb7f.aspx
--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a
Rick McGuire wrote:
Ok, I was able to reproduce this using the NODEBUG version and I think
I have a fix.
Just got a few minutes in between and updated to rev 4598, and yes, the
problem is fixed, thank you very much!
---rony
P.S.: Does it make any sense to file this as a bug with
No, I don't see any need for opening this as a bug. We don't like the
beta bug fixes in the changes file anyway..
Rick
On Tue, May 5, 2009 at 8:32 AM, Rony G. Flatscher
rony.flatsc...@wu-wien.ac.at wrote:
Rick McGuire wrote:
Ok, I was able to reproduce this using the NODEBUG version and I
Rick McGuire wrote:
On Mon, May 4, 2009 at 11:43 AM, Rony G. Flatscher
rony.flatsc...@wu-wien.ac.at wrote:
... cut ...
Question 1: Is there a way to get to the RexxInterpreter instance pointer or
RexxThreadContext pointer (which would allow for finding its RexxInterpreter
instance)
On Tue, May 5, 2009 at 12:19 PM, Rony G. Flatscher
rony.flatsc...@wu-wien.ac.at wrote:
Rick McGuire wrote:
On Mon, May 4, 2009 at 11:43 AM, Rony G. Flatscher
rony.flatsc...@wu-wien.ac.at wrote:
... cut ...
Question 1: Is there a way to get to the RexxInterpreter instance pointer or
The following code does not compile:
context-RaiseException1(Error_Incorrect_call_user_defined,
context-String(msg));
... error mesage:
BSF4Rexx.cc(2645) : error C2065: 'Error_Incorrect_call_user_defined' :
undeclared identifier
The identifier
Mark,
I was looking through the open bug list, and discovered we'd never
done anything with this patch:
http://sourceforge.net/tracker/?func=detailaid=2457111group_id=119701atid=684730
This looks like a good thing to apply, but unfortunately, my VMWare
installation decided to start misbehaving
On Tue, May 5, 2009 at 2:43 PM, Rick McGuire object.r...@gmail.com wrote:
I was looking through the open bug list, and discovered we'd never
done anything with this patch:
http://sourceforge.net/tracker/?func=detailaid=2457111group_id=119701atid=684730
This looks like a good thing to apply,
13 matches
Mail list logo
