Hi.
I can try do the testing. I am not developing in c so often so i am not
so experienced, I did not have need use such tool you mentioned yet. If
i will find something i will post it here.
martin
Dimuthu Gamage wrote:
On Jan 23, 2008 7:41 PM, martin spurek <[EMAIL PROTECTED]> wrote:
H Dimuthu. Yes, you are right, i am acutally using the nightly build for
the java and WSDL2C part. I updated it week or two ago from the version
i mentioned here and i did not remember it at the moment.
What i am actually trying to do:
I would like to create once one adb_EventDTO_t, one
adb_EventPerformed_t and reuse it and the memory free at the end of
program (i do not have to free the adb_EventDTO_t structure?
No, you don't have to. it will be freed when the request/response adb is freed,
) + always
(at every call) get response (it is created) and free of my own.
What i actually find strange on it: the memory footprint of the program
grows with every call the service very significantly (3 calls, initial
size 2808KB final size 2836KB). If i would use it in some project to run
on machine in scale of days it could be quite hardly usable, that is why
i am asking about the memory management in the generated stubs (either i
use adb* wrong or the memory management we could fix...).
Yea, I have not tested the memory management stuff on codegen
recently. It will be helpful if you can support on this with a tool
like valgrind or purify locating where the leaks are.
Thanks
Dimuthu
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
