Hi, this is the complete backtrace of my issue (amd64 system):
========================= (gdb) bt #0 0x00007ffff49fd3a9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x00007ffff4a004c8 in __GI_abort () at abort.c:89 #2 0x00007ffff4a368f4 in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7ffff4b2c103 "*** %s ***: %s terminated\n") at ../sysdeps/posix/libc_fatal.c:175 #3 0x00007ffff4abcb97 in __GI___fortify_fail (msg=msg@entry=0x7ffff4b2c09a "buffer overflow detected") at fortify_fail.c:31 #4 0x00007ffff4abbc20 in __GI___chk_fail () at chk_fail.c:28 #5 0x00007ffff4abcb07 in __fdelt_chk (d=<optimized out>) at fdelt_chk.c:25 #6 0x00007ffff7b91f88 in rfbProcessNewConnection (rfbScreen=rfbScreen@entry=0xa275c0) at sockets.c:407 #7 0x00007ffff7b924b8 in rfbCheckFds (rfbScreen=rfbScreen@entry=0xa275c0, usec=0) at sockets.c:306 #8 0x00007ffff7b897bd in rfbProcessEvents (screen=0xa275c0, usec=<optimized out>) at main.c:1101 #9 0x000000000049b801 in ?? () #10 0x00000000004605d2 in ?? () #11 0x0000000000410777 in ?? () #12 0x00007ffff49e9b45 in __libc_start_main (main=0x40d8d0, argc=11, argv=0x7fffffffe748, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffe738) at libc-start.c:287 #13 0x000000000041a78a in ?? () ========================= As Shaddy wrote I think that the new libvncserv0 library (0.9.9+dfsg-5) will solve this problem. This bug can be closed. Thanks to all... :-) Gianluca On Monday 28 April 2014 23:38:09 Shaddy Baddah wrote: > Hi, > > On 2014/04/24 04:02+0800, Florian Schlichting wrote: > > I'm downgrading this bug as I'm unable to reproduce it (doesn't > > affect everybody, does not make package unuseable as such) and I > > think it's unclear that this is actually a bug in x11vnc, rather > > than in one of the libraries it uses. The suggested patch is > > dubious: it is not changing any x11vnc code but instructs the build > > process to build its own version of libvncserver rather than use > > the shared library installed on the system. If that's really where > > the problem lies, this is a libvncserver bug. > > > > I notice both the Debian and Ubuntu reporters use i386 systems, > > whereas I'm on amd64. Has anybody tried recompiling x11vnc > > _without_ the patch (as in, just recompile the package against the > > current set of shared libraries) and checked if that's enough to > > fix things? And to produce a more useful backtrace it would > > probably help to have the > > libvncserver0-dbg and libc6-dbg packages installed. > > I have just filed Bug#746260 against libvncserver0 > (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746260) and if I am > right about that one, it confirms that you were right that the bug is > not in x11vnc, but in its main-use library. > > You are also probably right about system configuration, as I suspect I > encounter the bug because I don't have my nic configured for ipv6. No > bound ipv6 socket induces the buffer overflow error. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
