On Tuesday, January 28, 2020, 5:49:54 PM GMT+1, Mike Jumper 
<[email protected]> wrote: 
>> (gdb) bt 
>> #0  0x00007ffff7daabd0 in free () from /lib64/libc.so.6
>> #1  0x00007ffff699746d in rfbClientCleanup () from 
>> /usr/lib64/libvncclient.so.1
>> #2  0x00007ffff69ac26c in guac_vnc_client_free_handler 
>> (client=0x7ffff000b390) at client.c:92
>> #3  0x00007ffff7faa426 in guac_client_free (client=0x7ffff000b390) at 
>> client.c:195
>> #4  0x000055555555914e in guacd_client_free_thread (data=0x7ffff71bdbb0) at 
>> proc.c:219
>> #5  0x00007ffff7f87427 in start_thread () from /lib64/libpthread.so.0
>> #6  0x00007ffff7e242bf in clone () from /lib64/libc.so.6
>> (gdb) 
> 
> Which specific Linux distribution and version are you using? Which specific 
> version of libvncclient/libvncserver?

I'm using a "recent" Gentoo Linux (installed two weeks ago).

# uname -srvm
Linux 4.19.97-gentoo-x86_64 #1 SMP Mon Jan 27 11:32:41 CET 2020 x86_64

libvncserver-0.9.12-r3::gentoo 

libvncserver-0.9.12-r3 contains:
/usr
/usr/include
/usr/include/rfb
/usr/include/rfb/keysym.h
/usr/include/rfb/rfb.h
/usr/include/rfb/rfbclient.h
/usr/include/rfb/rfbconfig.h
/usr/include/rfb/rfbproto.h
/usr/include/rfb/rfbregion.h
/usr/lib64
/usr/lib64/libvncclient.so -> libvncclient.so.1
/usr/lib64/libvncclient.so.0.9.12
/usr/lib64/libvncclient.so.1 -> libvncclient.so.0.9.12
/usr/lib64/libvncserver.so -> libvncserver.so.1
/usr/lib64/libvncserver.so.0.9.12
/usr/lib64/libvncserver.so.1 -> libvncserver.so.0.9.12
/usr/lib64/pkgconfig
/usr/lib64/pkgconfig/libvncclient.pc
/usr/lib64/pkgconfig/libvncserver.pc
/usr/share
/usr/share/doc
/usr/share/doc/libvncserver-0.9.12-r3
/usr/share/doc/libvncserver-0.9.12-r3/AUTHORS.bz2
/usr/share/doc/libvncserver-0.9.12-r3/ChangeLog.bz2
/usr/share/doc/libvncserver-0.9.12-r3/NEWS.bz2
/usr/share/doc/libvncserver-0.9.12-r3/README.md.bz2
/usr/share/doc/libvncserver-0.9.12-r3/TODO.bz2

Vieri


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to