Bug 30952 – tightvnc (Xvnc) segfaults on amd64

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Andrew Johnson 2003-10-12 00:26:32 UTC]

Firstly, in order to compile tightvnc on amd64, patching to the
imake stuff is necessary. I'll attach the necessary patch -- it
was blatantly ripped from Mandrake.

While it seems to compile okay, the Xvnc program is segfaulting
on my system. I compiled tightvnc with debugging and generated a
backtrace. I'm still not sure what's causing it but I'll try to
play around and see if I can track it down. In the meantime,
confirmation of this crash or any other ideas from someone else
would be appreciated.

I should mention that half my system is compiled with -fPIC and
the other half not, so that's just another reason it'd be nice to
confirm this.

(gdb) run
Starting program: /var/tmp/portage/tightvnc-1.2.9-r1/work/vnc_unixsrc/Xvnc/programs/Xserver/Xvnc

Program received signal SIGSEGV, Segmentation fault.
0x0000002a95dce277 in strftime () from /lib/libc.so.6
(gdb) backtrace
#0  0x0000002a95dce277 in strftime () from /lib/libc.so.6
#1  0x00000000004bbfb5 in rfbLog (format=0x5d20f0 "Xvnc version %d.%d.%s\n")
    at init.c:947
#2  0x00000000004baca7 in InitOutput (screenInfo=0x71e620, argc=1,
    argv=0x7fbffff8b8) at init.c:402
#3  0x000000000041d826 in main (argc=1, argv=0x7fbffff8b8) at main.c:349

[Comment 1 Andrew Johnson 2003-10-12 00:28:35 UTC]

Created attachment 19122 [details, diff]
Patch to go in FILESDIR

[Comment 2 Andrew Johnson 2003-10-12 00:29:28 UTC]

Created attachment 19123 [details, diff]
Patch to ebuild

[Comment 3 Daniel Robbins (RETIRED) 2003-10-16 09:20:12 UTC]

I get a segmentation fault here as well.

[Comment 4 Daniel Ahlberg (RETIRED) 2003-10-31 08:08:28 UTC]

I couldn't get Xvnc to stop segfaultning no matter what x86_64 patch I used
either. Instead I started experimenting with the new beta4 source code. No
easy task since it requires to be built togheter with the XFree sources but
you can expect an ebuild during this weekend.

[Comment 5 Daniel Ahlberg (RETIRED) 2003-11-03 05:22:50 UTC]

Commited. Please report bugs and enhancements to me ([e-mail])

[Comment 6 Jason McGuiness 2005-02-06 17:45:20 UTC]

In tightvnc-1.3_alpha5 I get a coredump in running vncserver:

1. Rebuilt tightvnc with CFLAGS="-march=opteron -O0 -g -pipe", FEATURES+="nostrip", USE+="debug".
2. run "Xvnc :2 -desktop 'X' -httpd /usr/share/tightvnc/classes -auth /home/jason/.Xauthority -geometry 1024x768 -depth 24 -rfbwait 120000 -rfbauth /home/jason/.vnc/passwd -rfbport 5902 -core"

Examining the core file in GDB shows this:

(gdb) where
#0  0x0000002a95efb047 in strftime_l () from /lib/tls/libc.so.6
#1  0x00000000004bce52 in rfbLog (format=0x5d575d "Xvnc version %s\n")
    at init.c:956
#2  0x00000000004bbb59 in InitOutput (screenInfo=0x721aa0, argc=19,
    argv=0x7fbfffee68) at init.c:411
#3  0x000000000041d9f4 in main (argc=19, argv=0x7fbfffee68) at main.c:349
(gdb) q