> I would suggest that if you have found a scenario where you are pretty
> sure you always get the crash, you try that scenario using an
> interpreter built from trunk.
thank you very much for this idea!

Tried to create it, but got an error while building oodialog (using rev.
5135 from trunk):

        F:\work\svn\oorexx\main\trunk>makeorx BOTH PACKAGE
        rxapi.exe (process ID: 3576) killed successfully
        Building Rexxapi..
        Building Interpreter....
        Building OREXXOLE..
        Building Rexxutil..
        Building rxftp
        Building rexximage command launcher
        Building rexx command launcher
        Building rexxhide command launcher
        Building rexxpaws command launcher
        Building rexxc command launcher
        Building REXX.IMG ...
        Building RXSUBCOM and RXQUEUE..
        Building rxwinsys.dll
        Building RxSock..
        Building RxMath..
        Building RXREGEXP...
        Building OODIALOG..
        ***! Error occured !** : build halted

        ... cut (from Win32Rel.log) ...
 : fatal error C1083: Cannot open include file: 'oodText.hpp': No such file or 
        NMAKE : fatal error U1077: 'cl' : return code '0x2'

Probably that missing include file needs to be added to svn.



Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.
Oorexx-devel mailing list

Reply via email to