Bug#414307: xnest: Crashes with client Tulip
Package: xnest
Version: 2:1.1.1-20
Severity: important
Xnest consistently crashes with the application Tulip (Debian package
tulip, version 2.0.6-4). Simply create a new document.
Tulip on AMD64 also crashes xserver-xorg-core 2:1.1.1-19 on i386
during the same operation. Tulip on i386 also crashes the same
version of xserver-xorg-core on i386. This could be considered a much
more serious problem when it crashes a "real" X server; thankfully it
can be reproduced with Xnest.
A backtrace from the core file left by the Xnest follows. Please let
me know if there's any particular detailed information I can give that
will help.
Core was generated by `Xnest -geometry 838x1029 -query synthetic-forms'.
Program terminated with signal 11, Segmentation fault.
#0 0x00000000004fde07 in _mesa_shareContext ()
(gdb) bt
#0 0x00000000004fde07 in _mesa_shareContext ()
#1 0x00000000004bc0f4 in GlxInitVisuals ()
#2 0x00000000004bb366 in GlxInitVisuals ()
#3 0x000000000048e26a in GlxInitVisuals ()
#4 0x000000000048a524 in XETrapDispatch ()
#5 0x00000000004329e9 in dixDestroyPixmap ()
#6 0x00000000004435fd in NotImplemented ()
#7 0x00002ba424d404ca in __libc_start_main () from /lib/libc.so.6
#8 0x000000000041d84a in ?? ()
#9 0x00007fff866c6d98 in ?? ()
#10 0x0000000000000000 in ?? ()
Thanks,
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-custom-xen-1
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages xnest depends on:
ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries
ii libx11-6 2:1.0.3-5 X11 client-side library
ii libxau6 1:1.0.1-2 X11 authorisation library
ii libxdmcp6 1:1.0.1-2 X11 Display Manager Control Protoc
ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar
ii libxfont1 1:1.2.2-1 X11 font rasterisation library
xnest recommends no packages.
-- no debconf information
--
J.P. Larocque: <piranha@thoughtcrime.us>, <piranha@ely.ath.cx>
Reply to: