Bug 1092 - Xnest segfaults immediately
Summary: Xnest segfaults immediately
Status: RESOLVED DUPLICATE of bug 1404
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/DDX/Xnest (show other bugs)
Version: git
Hardware: Other Linux (All)
: lowest trivial
Assignee: Stefan Dirsch
QA Contact:
Depends on:
Reported: 2004-08-16 04:11 UTC by Stefan Dirsch
Modified: 2004-09-18 00:06 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:


Description Stefan Dirsch 2004-08-16 04:11:01 UTC
# Xnest :1 
Segmentation fault 
# gdb Xnest 
Program received signal SIGSEGV, Segmentation fault. 
0x00bd1642 in ?? () 
(gdb) bt 
#0  0x00bd1642 in ?? () 
#1  0x080fb869 in getDrawableDamageRef () 
#2  0x083c3218 in ?? () 
#3  0xbfffea08 in ?? () 
#4  0x080fecbb in damagePaintWindow () 
Previous frame inner to this frame (corrupt stack?) 
Comment 1 Kevin E. Martin 2004-08-17 08:56:03 UTC
I cannot reproduce this segfault.  A problem like this occurred last week (bug
961) and was fixed.  Are you using the latest version in CVS?
Comment 2 Stefan Dirsch 2004-08-17 09:37:42 UTC
Yes, it was CVS of yesterday and I verified with CVS of today. 
Comment 3 Kevin E. Martin 2004-08-17 09:42:38 UTC
Okay.  Since I cannot reproduce this problem.  Could you please track it down
and see if you can find out where the problem is?
Comment 4 Stefan Dirsch 2004-08-17 10:47:25 UTC
It's crashing in xc/programs/Xserver/miext/damage/damage.c 
--> miext/damage/getDrawableDamageRef: 
    PixmapPtr   pPixmap; 
    if (pDrawable->type == DRAWABLE_WINDOW) 
        ScreenPtr   pScreen = pDrawable->pScreen; 
        pPixmap = 0; 
        if (pScreen->GetWindowPixmap) 
            pPixmap = (*pScreen->GetWindowPixmap) ((WindowPtr)pDrawable); 
At this line ... 
Comment 5 Stefan Dirsch 2004-08-20 02:00:52 UTC
The segfault of Xnest is somewhat related to the (physical hardware) Xserver or 
the machine, on which it is started. Starting the same Xnest on another 
(physical hardware) Xserver, which is running on another machine, works fine. 
Therefore I think that this is a misconfigured or pretty broken Xserver 
configuration or broken system. I assign this bugreport to myself, as nobody 
else will be able to reproduce this problem and set this to trivial with lowest 
Comment 6 Stefan Dirsch 2004-09-18 15:31:24 UTC

*** This bug has been marked as a duplicate of 1404 ***

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.