Summary: | XCopyArea causes segfault with bad parameters | ||||||
---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Sami Farin <safari-ml-freedesktop-bugzilla-kv7oy2vp4mc4jvudr6vccb7oetrzzqe7fwnhahno> | ||||
Component: | Server/General | Assignee: | Xorg Project Team <xorg-team> | ||||
Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||
Severity: | critical | ||||||
Priority: | high | CC: | jesserayadkins, kasper.peeters | ||||
Version: | 6.99.99.902 (7.0 RC2) | ||||||
Hardware: | x86 (IA32) | ||||||
OS: | Linux (All) | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
Sami Farin
2005-12-12 12:13:20 UTC
Created attachment 4099 [details] XCopyArea crashtest $ gcc -O2 -o crash crash.c -lXpm -lXext -lX11 $ ./crash [ wait some seconds till the bar crashes thru the borders :-q ] Original source at ftp://ftp.fi.debian.org/pub/debian/pool/main/w/wmcpu/wmcpu_1.3.orig.tar.gz Is this the same bug as #6642? It would be good to know if the fix there resolves this problem. I might bother recompiling Xorg when Fedora releases Xorg src.rpm which contains working server, as in "no 0 MHz problems". https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=188770 (Looks I have deleted server version 1.0.1 src.rpm ...) I wasted six hours playing with Fedora's latest Xorg (xorg-x11-server-1.0.99.903-1) which has fix mentioned in #6642, but I get segfault with it, too. Fedora's Xorg also gives me max 55 Hz refresh rate and latest evdev does not work, so I am back to Xorg 1.0.1. Fedora's xorg 1.1.1-55 with today's i810 modesetting branch do not crash. Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future. I tried this yesterday using xserver 1.9 and Ubuntu 10.10. No crash, but I did see a message about an XIO error on app closure. This looks fixed, so I'm closing it like it is. Reopen if I'm wrong. |
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.