-
Hi all,
The header file rexxapitypes.h defines C9X Standard integer types unconditionally. Unfortunately we are using a third party library that defines these types too.
As a result the build of our project fails due to definition conflicts! (error C2371: 'int8_t' : redefinition; different basic types )
We brings to your awareness that these types are already present under some platforms...
2009-09-29 12:25:02 UTC in Open Object Rexx
-
The version i have installed is the latest version V4.0 ooRexx-4.0.0.i586.exe available.
The platform i used is WinXP-32 bit.
To use the following sample CvHello set the Hello.rex in C:\, then run CvHello.
I have engage a purify integration and detects some leaks on RexxSetProcessMessages and RexxPullQueue.
You can see the report in attachment. I think this is this issue that make troubles...
2009-09-09 13:14:17 UTC in Open Object Rexx
-
We are testing Rexx ooRexx-4.0.0-4881 RC.
Test is done on Windows XP SP4.
When RexxStart is called via a C++ program the RxAPi memory increases
and when this program is sleeping the memory is never free.
Not the same issue as the bug 2817468.
Step to reproduce (See attached sample)
Set Hello.rex in C:\\
Start the CvHello.exe
Check RxApi memory. The memory increases.
Look the memory...
2009-07-08 16:37:37 UTC in Open Object Rexx
-
We are testing the ooRexx-4.0.0-4861 RC.
A fix comitted in revision 4881 would allow us to go further in our tests.
Is it possible to have a new release of the ooRexx v4.0 RC that integrate this revision?
Thanks in advance,
Best regards.
Laurent Crepel.
2009-07-07 17:15:49 UTC in Open Object Rexx
-
You will find enclosed a complete sample (display 'Cv Hello') that call rexxStart, and the associated CvHello.exe
To reproduce :
Set Hello.rex in C:\
Launch the CvHello.exe or debug it with viual.
At each call you'll see memory and handle increasing.
I think memory leaks is due to parameter parsing.
If RexxStart is called with only function name memory is stable.
2009-07-06 16:08:21 UTC in Open Object Rexx
-
Moreover, an important point is that memory usage increases at each called of RexxQueryMacro and RexxStart and it is never deallocated.
2009-07-06 14:34:49 UTC in Open Object Rexx
-
We are testing Rexx ooRexx-4.0.0-4861 RC.
Test is done on Windows XP SP4.
Each time there is a call to RexxApi from C/C++ program, a new handle is used by program and never
released.
The function tested is RexxQueryMacro and RexxStart.
In version 3.2, memory and Handles are fixed.
See below how we use it (3.2 reference API) :
RXSYSEXIT vExit[2]={0}; // UserExit pour l'affichage.
2009-07-06 14:18:09 UTC in Open Object Rexx
