[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#388681: marked as done (x11vnc: segfault)

Your message dated Sat, 8 Aug 2009 10:41:47 +0200
with message-id <6a2e33620908080141o3c3ceadas8b7ea7a59b11120c@mail.gmail.com>
and subject line x11vnc: segfault
has caused the Debian Bug report #388681,
regarding x11vnc: segfault
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
388681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=388681
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: x11vnc
Version: 0.7-1
Severity: important

hi,

here's the last lines of the trace:

21/09/2006 22:57:37 setting up 32 cursors...
21/09/2006 22:57:37   done.
21/09/2006 22:57:37 Autoprobing TCP port 
21/09/2006 22:57:37 Autoprobing selected port 5900
21/09/2006 22:57:37 created 40 tile_row shm polling images.
21/09/2006 22:57:37 screen setup finished.
21/09/2006 22:57:37 
21/09/2006 22:57:37 The VNC desktop is gb:0
PORT=5900
21/09/2006 22:57:58 Got connection from client 192.168.2.252
21/09/2006 22:57:58   other clients:
21/09/2006 22:57:58 denying client: 192.168.2.252 does not match 192.168.2.52
21/09/2006 22:57:58 Client 192.168.2.252 gone
21/09/2006 22:57:58 Statistics:
21/09/2006 22:57:58   framebuffer updates 0, rectangles 0, bytes 0
caught signal: 11

program was started as 'x11vnc -allow 192.168.2.52 -display :0', then from
host 192.168.2.52 a connection was attempted with 
'VNC viewer for X version 4.0 - built Sep  4 2004 00:11:32'

Running from gdb:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1211075168 (LWP 28654)]
0xb7d870dd in mallopt () from /lib/tls/libc.so.6
(gdb) bt
#0  0xb7d870dd in mallopt () from /lib/tls/libc.so.6
#1  0xb7d86f6e in mallopt () from /lib/tls/libc.so.6
#2  0xb7d85dcb in free () from /lib/tls/libc.so.6

#3  0x0806b9fc in ?? ()
#4  0x08129270 in ?? ()
#5  0xbf8e7550 in ?? ()
#6  0x0000000c in ?? ()
#7  0x00000003 in ?? ()
#8  0x00000004 in ?? ()
#9  0xb7dfe1f0 in inet_ntoa () from /lib/tls/libc.so.6
#10 0x0806bd8e in ?? ()
#11 0x08119ca8 in ?? ()
#12 0x00000009 in ?? ()
#13 0x00000000 in ?? ()
#14 0x000000fc in ?? ()
#15 0x08119ca8 in ?? ()
#16 0x00000009 in ?? ()
#17 0xbf8e7698 in ?? ()
#18 0x0806fca9 in ?? ()
#19 0x08119ca8 in ?? ()
#20 0x00000009 in ?? ()
#21 0x00000001 in ?? ()
#22 0xbf8e75d0 in ?? ()
#23 0x00000004 in ?? ()
#24 0xb7ea28a0 in ?? () from /usr/X11R6/lib/libX11.so.6
#25 0xb7f72510 in ?? ()
#26 0xb7ed0f91 in _XFlush () from /usr/X11R6/lib/libX11.so.6
Previous frame inner to this frame (corrupt stack?)

where libX11 is: 	6.9.0.dfsg.1-6~bpo.4
      libc.so.6 is:	2.3.2.ds1-22sarge4
      
Also, couldn't connect from xvnc4viewer on Etch x11vnc 'cause of 
'reset by peer(104)'. Might be related or not, worth noting though.

Connecting from the allowed IP worked fine from a Woody pc, at least once. 


thanks

-- paolo

--- End Message ---
--- Begin Message --- 
old bug.
please re-open if it's still reproducible with a recent release.

--- End Message ---
Reply to: