Bug 27133

Summary:

X11 crashed if I run a wine test case (pixman-0.17.2)

Product:

xorg

Reporter:

Toralf Förster <toralf.foerster>

Component:

Lib/other

Assignee:

Xorg Project Team <xorg-team>

Status:

RESOLVED FIXED

QA Contact:

Xorg Project Team <xorg-team>

Severity:

normal

Priority:

medium

Version:

7.5 (2009.10)

Hardware:

x86 (IA32)

OS:

Linux (All)

Whiteboard:

i915 platform:

i915 features:

Attachments:

Description	Flags
strace output	none

Description Toralf Förster 2010-03-17 09:32:36 UTC

If I Run this :

tfoerste@n22 ~ $ cd ~/devel/wine-git/programs/winetest/
tfoerste@n22 ~/devel/wine-git/programs/winetest $ strace -o ~/strace.out wine user32_test.exe win

I'm faced immediately with the login screen of kdm.

I can deliver backtraces however I dunno which component is affected and how I should start it with gdb.

My Gentoo system :

tfoerste@n22 ~ $ uname -a
Linux n22 2.6.31.12 #8 SMP Thu Mar 11 15:08:22 CET 2010 i686 Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz GenuineIntel GNU/Linux

[IP-] [  ] x11-base/xorg-drivers-1.7:0
[IP-] [  ] x11-base/xorg-server-1.7.5.902-r1:0
[IP-] [  ] x11-drivers/xf86-input-evdev-2.3.2:0
[IP-] [  ] x11-drivers/xf86-input-keyboard-1.4.0:0
[IP-] [  ] x11-drivers/xf86-input-mouse-1.5.0:0
[IP-] [  ] x11-drivers/xf86-video-intel-2.10.0-r1:0
[IP-] [  ] media-libs/mesa-7.7.1_rc1:0

Comment 1 Toralf Förster 2010-03-17 09:33:03 UTC

Created attachment 34153 [details]
strace output

Comment 2 Toralf Förster 2010-03-19 07:45:40 UTC

This is the backtrace of the X process of xorg-server 1.7.6 if I run the command
$>sleep 300; wine /home/tfoerste/devel/wine-git/./dlls/user32/tests/user32_test.exe.so win
within a X11 session, switched to the console and attached gdb to the process /usr/bin/X :

...
Program received signal SIGABRT, Aborted.
0xb76ef424 in __kernel_vsyscall ()
#0  0xb76ef424 in __kernel_vsyscall ()
#1  0xb72176e0 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#2  0xb7218f15 in *__GI_abort () at abort.c:88
#3  0xb721090e in *__GI___assert_fail (assertion=0xb75c6820 "region->extents.x1 < region->extents.x2",
    file=0xb75c66c2 "pixman-region.c", line=1093, function=0xb75c68a7 "pixman_set_extents") at assert.c:78
#4  0xb7577dc9 in pixman_set_extents (region=0xa993150) at pixman-region.c:1093
#5  0x0809caec in miTranslateRegion (pReg=0xa993150, x=5, y=25) at miregion.c:1563
#6  0xb710ab41 in uxa_poly_fill_rect (pDrawable=0x925c860, pGC=0xa947280, nrect=2, prect=0xa9924f0) at uxa-accel.c:684
#7  0xb7109b7c in uxa_poly_segment (pDrawable=0x925c860, pGC=0xa947280, nseg=2, pSeg=0xa98bd68) at uxa-accel.c:659
#8  0x0811b235 in damagePolySegment (pDrawable=0x925c860, pGC=0xa947280, nSeg=2, pSeg=0xa98bd68) at damage.c:1191
#9  0x0807a4e8 in ProcPolySegment (client=0xa993238) at dispatch.c:1849
#10 0x0807c5df in Dispatch () at dispatch.c:439
#11 0x08065de5 in main (argc=3, argv=0xbf89d2d4, envp=Cannot access memory at address 0x57d9
) at main.c:285
A debugging session is active.
...

Comment 3 Søren Sandmann Pedersen 2010-03-20 15:19:03 UTC

Thanks for the bug report. 

This is basically an X server bug triggering asserts in pixman. Those asserts are not active in later versions of pixman, for example 0.17.12 (a beta release) or 0.16.6 (a stable release).

If you still see the problem with either of those releases, then feel free to reopen 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.