- FreeBSD 12.2-RELEASE-p1 running on amd64 architecture
- libvncserver 0.9.12_2 - binary package installed from 'pkg install'
After building and running the SDLvncviewer.c example program at:
I attempted to connect to any TightVNC server running on Windows 7 or 10 and receive the following error (gdb output):
Starting program: /usr/home/will/Projects/sdl-vnc-viewer/sdlvncviewer 192.168.0.128
08/01/2021 13:52:51 VNC server supports protocol version 3.8 (viewer 3.8)
08/01/2021 13:52:51 We have 2 security types to read
08/01/2021 13:52:51 0) Received security type 2
08/01/2021 13:52:51 Selecting security type 2 (0/2 in the list)
08/01/2021 13:52:51 1) Received security type 16
08/01/2021 13:52:51 Selected Security Scheme 2
Program received signal SIGBUS, Bus error.
0x000000080026b3e5 in rfbClientDesKey () from /usr/local/lib/libvncclient.so.1
#0 0x000000080026b3e5 in rfbClientDesKey () from /usr/local/lib/libvncclient.so.1
#1 0x000000080026afba in rfbClientEncryptBytes () from /usr/local/lib/libvncclient.so.1
#2 0x000000080025c9d9 in ?? () from /usr/local/lib/libvncclient.so.1
#3 0x000000080025b4e8 in InitialiseRFBConnection () from /usr/local/lib/libvncclient.so.1
#4 0x0000000800272bee in rfbInitClient () from /usr/local/lib/libvncclient.so.1
#5 0x0000000000202de1 in main (argc=2, argv=0x7fffffffda48) at sdlvncviewer.c:446
This appears to be an issue only on FreeBSD as building and running this works fine on Linux.
Build command line was:
$ cc -Wall -o sdlvncviewer sdlvncviewer.c -I/usr/local/include -I/usr/include -I/usr/local/include/SDL2 -L/usr/local/lib -lvncclient -lSDL2 -O0 -g
$ cc --version
FreeBSD clang version 10.0.1 (firstname.lastname@example.org:llvm/llvm-project.git llvmorg-10.0.1-0-gef32c611aa2)
Thread model: posix
Thank you! :-)
Try building libvncserver from Ports. We are on 0.9.13 now.
If that does not work, try rebuilding with SASL support.
Please report whether those two worked for you or now.
(In reply to Neel Chauhan from comment #1)
I would rather not mix Ports and Packages. Doing so has caused much pain in the past. Should I file a bug report to update the libvncserver package to 0.9.13?
Closing because it appears the libvncserver binary package has been updated. I am no longer seeing this crash.
Thank you! :-)