Bug 961 - Xnest crashes in damagePaintWindow()
Summary: Xnest crashes in damagePaintWindow()
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/DDX/Xnest (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: high blocker
Assignee: Xorg Project Team
QA Contact:
: 1292 1512 (view as bug list)
Depends on:
Blocks: 351
  Show dependency treegraph
Reported: 2004-07-31 21:10 UTC by Roland Mainz
Modified: 2004-10-02 19:25 UTC (History)
8 users (show)

See Also:
i915 platform:
i915 features:


Description Roland Mainz 2004-07-31 21:10:29 UTC
2004-08-01 CVS trunk on SuSE 9.1/AMD64, Xnest crashes like this:
-- snip --
% gdb --args ./Xnest -audit 4 -ac :40
GNU gdb 6.1
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "x86_64-suse-linux"...Using host libthread_db library

(gdb) run
Starting program: /home/gisburn/projects/xorg/work002/xc/programs/Xserver/Xnest
-noreset -audit 4 -ac :40
Unable to initialize XKEYBOARD extension.
Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, removing from
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from

Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
(gdb) where
#0  0x0000000000000000 in ?? ()
#1  0x00000000004ff4e2 in GetDrawablePixmap (pDrawable=0xac3820) at damage.c:71
#2  0x0000000000504051 in damagePaintWindow (pWindow=0xac3820,
prgn=0x7fbffff350, what=0) at damage.c:1516
#3  0x000000000050aa4e in miWindowExposures (pWin=0xac3820, prgn=0x7fbffff350,
other_exposed=0x0) at miexpose.c:564
#4  0x000000000046595e in xnestWindowExposures (pWin=0xac3820,
pRgn=0x7fbffff350, other_exposed=0x0) at Window.c:448
#5  0x00000000004134d9 in MapWindow (pWin=0xac3820, client=0xa7b630) at
#6  0x000000000040dbb9 in InitRootWindow (pWin=0xac3820) at window.c:511
#7  0x000000000040ab6b in main (argc=6, argv=0x7fbffff538, envp=0x7fbffff570) at
-- snip --
Comment 1 Kevin E. Martin 2004-08-08 19:16:11 UTC
I have not been able to reproduce this one on an IA-32 box.  There have been
quite a few changes since the bug report was filed, so I don't know if this
still occurs.  Please verify that it still happens on your AMD64 box.
Comment 2 Kevin E. Martin 2004-08-10 21:09:19 UTC
Keith Packard made a comment in bug 1032 that perhaps DamageSetup was not being
called, which might have been happening here as well before Keith checked in his
new damage based misprite code (which calls DamageSetup for xnest).

That would explain why it failed previously and now seems to work.
Comment 3 Roland Mainz 2004-08-11 08:12:54 UTC
Xnest seems to work again with 2004-08-11-trunk on IA32, I still have to test
AMD64 when I am back...
Comment 4 Keith Packard 2004-08-11 15:43:53 UTC
Xnest was initializing the screen in the wrong order.  I fixed that and it seems
to work fine now.  I also fixed Damage to deal with Xnest's lack of
pCompositeClip in GCs and the lack of window pixmaps.  Xnest will need
significant redesign to support Composite though.
Comment 5 Roland Mainz 2004-10-03 12:25:00 UTC
*** Bug 1292 has been marked as a duplicate of this bug. ***
Comment 6 Roland Mainz 2004-10-03 12:25:41 UTC
*** Bug 1512 has been marked as a duplicate of this bug. ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.