crash
James "Wez" Weatherall
jnw22 "at" cam.ac.uk
Tue, 06 Jul 1999 11:15:33 +0000
> Anybody got this before?
>
> general protection: 0000
> CPU: 0
> EIP: 0010:[<0014a6df>]
> EFLAGS: 00010006
> eax: 003618ac ebx: 010226e8 ecx: 003618ac edx: 00000005
> esi: 00000202 edi: 000000f1 ebp: 00000800 esp: 00b99ed4
> ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
> Process Xvnc (pid: 987, process nr: 49, stackpage=00b99000)
> Stack: 003618ac 00361810 000000f1 0014a702 00361810 00361810 001470bc
> 00361810
> 00361810 00000000 00000800 000000f1 001516dd 00361810 00b99f5c
> 000000f1
> 00000800 00000000 000000f1 0137e200 0137e290 08167a24 00138c7e
> 0137e290
> Call Trace: [<0014a702>] [<001470bc>] [<001516dd>] [<00138c7e>]
> [<00123b9b>] [<0010a96d>]
> Code: e8 a8 7c fc ff 83 c4 04 56 9d 89 d8 5b 5e c3 89 f6 53 8b 5c
>
> It occurs on a linux-machine (Cyrix x86, Kernel 2.0.36) acting as
> vnc-server after the first mouse-movements on the client. It occurs
> independent from the kind of vnc-client and independent from the
> windowmanager running on the vnc-server. Even without windowmanager.
>
> Without mouse-movements the server crashes too, but it may take a while.
> Sometimes i even get it work for a few minutes inspite of using the
> mouse and the keyboard.
>
> No problems with normal X-Server.
>
> No problems on other machines, very nice tool.
>
> Ingo Wichmann
Which binary are you using (or did you recompile?) Could it be an
instruction set thing, in which case using a 386 binary rather than a
Pentium binary may help (assuming you're using a Pentium binary..)?
Just a thought!
James "Wez" Weatherall
--
- Queens' College MCR Entertainments Officer -
Laboratory for Communications Engineering, Cambridge - Tel : 766513
AT&T Labs Cambridge, UK - Tel : 343000
---------------------------------------------------------------------
The VNC mailing list - see http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------