Hej Per On Mon, Oct 02, 2006 at 01:36:00PM +0200, Per Olofsson wrote: > Hej Ola! > > Ola Lundqvist: > > As this is a amd64 specific problem and I do not have access to an amd64 > > machine I'll need help from you. > > Sure. > > > I also wonder if this is really a grave bug as it work on other > > architectures. > > I would like to set it to important. > > If you ask me, providing an amd64 package of tightvncserver in etch > which does not work is quite confusing, so I think it's a grave > severity bug. But you can, however, remove the amd64 package and then > downgrade the bug. (I think you can (build-)depend on not+amd64 or > something like that.)
Do you know the syntax for such a build dependency? > > So what do I need help with? > > * A gdb backtrace > > With debugging symbols: > > #0 0x0000000000447975 in WaitForSomething (pClientsReady=0x7fffa57330e0) > at WaitFor.c:534 > #1 0x0000000000000000 in ?? () > > > * or even better a patch > > I tried to find a fix, but I can't make sense of the code. It's ugly > as hell, IMHO. I fully agree! > 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). Hmm. I see. Well that is not that easy to find. Regards, // Ola > -- > Pelle > > -- --------------------- Ola Lundqvist --------------------------- / [EMAIL PROTECTED] Annebergsslingan 37 \ | [EMAIL PROTECTED] 654 65 KARLSTAD | | +46 (0)54-10 14 30 +46 (0)70-332 1551 | | http://www.opal.dhs.org UIN/icq: 4912500 | \ 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]
