ports/116385: net/vnc using vnc.so crashes Xorg 7.3 when remote computer connects

Steve Roome steve at pepcross.com
Sat Feb 16 22:51:15 PST 2008


Does anyone have vnc (loaded as .so by the Xserver) working at the moment?

I just tried it from packages and I got this backtrace out of the
coredump it gave me:

.... lots of unexciting loading stuff ....
Loaded symbols for /libexec/ld-elf.so.1
#0  0x28529493 in kill () from /lib/libc.so.6
[New LWP 100085]
(gdb) bt
#0  0x28529493 in kill () from /lib/libc.so.6
#1  0x2844d212 in raise () from /lib/libpthread.so.2
#2  0x2852813c in abort () from /lib/libc.so.6
#3  0x0809b376 in ddxGiveUp ()
#4  0x08193474 in AbortServer ()
#5  0x0819371e in FatalError ()
#6  0x080b7171 in xf86SigHandler ()
#7  0x28453e87 in sigaction () from /lib/libpthread.so.2
#8  <signal handler called>
#9  0x285ecbcf in XserverDesktop::pointerEvent () from /usr/local/lib/modules/extensions//vnc.so
#10 0x28607e90 in rfb::SMsgReader::readPointerEvent () from /usr/local/lib/modules/extensions//vnc.so
#11 0x28602313 in rfb::VNCSConnectionST::processMessages () from /usr/local/lib/modules/extensions//vnc.so
#12 0x285f6154 in rfb::VNCServerST::processSocketEvent () from /usr/local/lib/modules/extensions//vnc.so
#13 0x285edd91 in XserverDesktop::wakeupHandler () from /usr/local/lib/modules/extensions//vnc.so
#14 0x285e5415 in vncExtensionInit () from /usr/local/lib/modules/extensions//vnc.so
#15 0x08087db3 in WakeupHandler ()
#16 0x08187414 in WaitForSomething ()
#17 0x08083f07 in Dispatch ()
#18 0x0806de16 in main ()
(gdb) 

My guess would be that VNC has the wrong idea of an XEvent Structure
but I'm not able to look into it much more (I'm running this setup on
a rather cramped box with only flash storage). Does this work if built
from ports yet, I just pkg_add -r'd it all down here.

I wasn't bitten by the missing font-alias package due to it being
supplied by something else, but that problem is still there also
I think.
[ ports/118293: net/vnc Xvnc won't run without fonts.alias installed ]

Anyone else trying to get this fixed ?

--
    Steve Roome




More information about the freebsd-x11 mailing list