In the file vncService.cpp we can see a strange comment: // *** If we don't kill the process directly here, then // for some reason, WinVNC crashes... ExitProcess(0); Digging this problem, I found that it comes from kernel32.dll It writes a value in the stack (!). The workaround is to have "free space" in the stack. This allow the written value to be in a safe place. With Borland compiler, a simple char foo; seems to be ok. For security, I use char ms_bug[32]; :-) When you compile you have a warning saying ms_bug is never used but, hey, this is the goal.
-- ______________________________ David TAILLANDIER - SOLEIL VERT --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------
