Bug 1660 - Enabling Damage causes SigSegV
Summary: Enabling Damage causes SigSegV
Status: CLOSED WONTFIX
Alias: None
Product: xorg
Classification: Unclassified
Component: Lib/other (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Keith Packard
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-17 17:11 UTC by Felix Schulte
Modified: 2011-10-15 17:35 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Felix Schulte 2004-10-17 17:11:10 UTC 
X Release 6.8, I tried to enable the Xfixes and Damage extensions in Xprt. Just
removing the Damage and Xfixes symbols from the PRINT_ONLY_SERVER section in
miinitext.c delivers the following crash:

Program received signal SIGSEGV, Segmentation fault.
0x08181926 in damagePolyFillRect (pDrawable=0x89835b0, pGC=0x89833b0, 
    nRects=1, pRects=0xbffff1f8) at damage.c:1179
1179        if (nRects && checkGCDamage (pDrawable, pGC))
(gdb) where
#0  0x08181926 in damagePolyFillRect (pDrawable=0x89835b0, pGC=0x89833b0, 
    nRects=1, pRects=0xbffff1f8) at damage.c:1179
#1  0x08081960 in CreateDefaultStipple (screenNum=0) at gc.c:1096
#2  0x0805e17d in main (argc=8, argv=0xbffff2a4, envp=0xbffff2c8) at main.c:386
#3  0x400ef8ae in __libc_start_main () from /lib/libc.so.6
Comment 1 Roland Mainz 2004-12-04 19:58:44 UTC 
keith:
Any idea what is going wrong here ?
Comment 2 Keith Packard 2004-12-04 22:42:10 UTC 
Sorry, I don't have any idea.  It looks like this is the first drawing done in
the server at startup time though.  Xprt is a mystery to me.
Comment 3 Roland Mainz 2005-01-23 19:50:33 UTC 
(In reply to comment #2)
>  Xprt is a mystery to me.

OK, what info are you missing ? :)
Comment 4 Jeremy Huddleston Sequoia 2011-09-24 16:56:56 UTC 
Old bug.  Is this still a problem?
Xprint is no longer supported.  If you can provide a patch, we'll commit it.

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.