Maurizio,
Tcl_Finalize() is supposed to work, and if it does now work
something is still broken in the windows version. Omitting
Tcl_Finalize() is removeing the symptom, not the cause. It
is not unlikely that something else will have the same
problem due to this cause.
When Tcl_Finalize()
Dear Gustav,
I understand perfectly than omitting the function is
removing the symptom and not the cause,
but process/service wise having Tcl_Finalize in that particular place (where
the process/service is about to end) or not having it doesn't make any
difference. The Operating
YES. I do agree that executing or not executing the exit handlers may make a
difference..
Just to help me in my troubleshooting can you tell me if and where these
handlers are registered.
I am digging into Tcl_Finalize.. J
Thank you,
Maurizio
From: AOLserver Discussion
It is me again.
Well I noticed that the change I suggested about Tcl_Finalize did not make
it into CVS HEAD.
If it doesn't go there, I am afraid I will have to anyhow introduce it
myself in my distribution.
I need to have a working system. With that call still in, the service can't
(CANNOT) be
Dear Dossy,
Your proposal of your wrapper sounds good to me.
Why do not we insert that in the codebase? Till we understand better the
issue?
Next week I am going to redo some testing also in Win32 and I will let you
know..
Thank you very much,
Maurizio
From:
Hello all
I did some tests on Windows 32.
Tcl_Finalize prevents the proper stopping of the service also on Windows 32.
So the proper mod was and still is:
// Conditional compilation clause added by M. Martignano on the 05/08/2011
#ifndef _WIN32
Tcl_Finalize();
#endif
I vaguely remember never figuring this out either and deciding to ifdef it out.
In practice it doesn't do much -- I've never come across a on-exit handler
that really needed fire. Curious if anyone has.
Jim
Sent from a phone
On Aug 6, 2011, at 3:29 PM, Maurizio Martignano
