Summary: | xlib text test cases crash on mac (macports 1.4.0) | ||
---|---|---|---|
Product: | cairo | Reporter: | Brian Ewins <Brian.Ewins> |
Component: | xlib backend | Assignee: | Carl Worth <cworth> |
Status: | RESOLVED FIXED | QA Contact: | cairo-bugs mailing list <cairo-bugs> |
Severity: | normal | ||
Priority: | medium | ||
Version: | 1.4.3 | ||
Hardware: | Other | ||
OS: | Mac OS X (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Brian Ewins
2007-04-03 09:06:40 UTC
Chris made a suggestion on IRC that this was a possible fix: http://gitweb.freedesktop.org/?p=users/ickle/cairo.dirty;a=commit;h=90f8d34fb63ad41e1b38edd12fe9eb5bd9b6e678 It's not the same bug. I've nuked my dp setup, and reinstalled it clean (to do this you need to uninstall Apple X11 and install cairo, automake, libtool, and git-core). Testing with this quickly 1.4.0 is still working and passing the text tests, while HEAD crashes as above. I expect bisection will get me to the same place, the crash reports are still the same. uh, somewhat ambiguous in that last comment - it is cairo 1.4.0 that works correctly. Chris' latest patch: http://gitweb.freedesktop.org/?p=users/ickle/cairo;a=commitdiff;h=6f4ee099385a58e40d5b04ae4bf389508a874c9e resolves the bug for me. I've pushed another version of the patch that Chris created, (by splitting the original up into about four pieces---two of which I've pushed). Here's the piece that should fix this bug: http://gitweb.freedesktop.org/?p=cairo;a=commitdiff;h=8c9f0f607b992c47b555b5eaff3c599a8c1eac57 Please test and let us know. Thanks, -Carl (In reply to comment #4) > I've pushed another version of the patch that Chris created, (by splitting the > original up into about four pieces---two of which I've pushed). Here's the > piece that should fix this bug: > > http://gitweb.freedesktop.org/?p=cairo;a=commitdiff;h=8c9f0f607b992c47b555b5eaff3c599a8c1eac57 > > Please test and let us know. > > Thanks, > > -Carl > Thanks, that's fixed 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.