Hi Thanks for the help. I have now unapplied that patch and will upload a new version in a short while.
To Truxton Fulton: Could you revise this patch to determine why it do not work on amd64. I liked it. I assume that it can have something to do with the fd_set calls that you mentioned in the mail to me. Unfortunatly I have to remove it right now in order for it to not segfault on amd64. Roland and Per: Please try this new version that is uploaded to debian today. Regards, // Ola On Mon, Oct 02, 2006 at 05:02:08PM +0200, Roland Rosenfeld wrote: > On Mon, 02 Oct 2006, Per Olofsson wrote: > > > What happens, I think, is that the Dispatch() function allocates the > > array pClientsReady on the stack, with a size of 1000 > > (MaxClients). But WaitForSomething(), for some reason, writes > > outside the array boundary (which explains why the stack is > > corrupt). > > Seems that the maxclients patch is part of the problem. If you remove > this patch, Xtightvnc doesn't die with a segfault any longer. > > Tschoeeee > > Roland > -- --- Ola Lundqvist systemkonsult --- M Sc in IT Engineering ---- / [EMAIL PROTECTED] Annebergsslingan 37 \ | [EMAIL PROTECTED] 654 65 KARLSTAD | | http://opalsys.net/ Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --------------------------------------------------------------- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
