Bug 96666 - XQuartz 2.7.9 and 2.7.10(beta) cause KARMA tools to seg fault
Summary: XQuartz 2.7.9 and 2.7.10(beta) cause KARMA tools to seg fault
Status: RESOLVED DUPLICATE of bug 96292
Alias: None
Product: XQuartz
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 2.7.9 (xserver-1.17.4)
Hardware: x86-64 (AMD64) Mac OS X (All)
: medium normal
Assignee: Jeremy Huddleston Sequoia
QA Contact: Jeremy Huddleston Sequoia
Depends on:
Reported: 2016-06-24 12:47 UTC by Tim Davis
Modified: 2016-07-04 07:18 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Description Tim Davis 2016-06-24 12:47:18 UTC
On Mac OS-X El Capitain, after upgrading from XQuartz 2.7.8 to 2.7.9 the software tools from the KARMA package (http://www.atnf.csiro.au/computing/software/karma/) now seg fault when opened.

I tried to upgrade to 2.7.10beta, to check if that helped. It did not, but at least provided the following error:

==1846==ERROR: AddressSanitizer: SEGV on unknown address 0x00000000001c (pc 0x000106cb7015 bp 0x7fff58f6d210 sp 0x7fff58f6ceb0 T0)
    #0 0x106cb7014 in _ImageDisplay_Initialise (/usr/local/karma/lib/libkarmawidgets.1.7.20.dylib+0x1e014)
    #1 0x1070a4285 in CallInitialize (/usr/X11/lib/libXt.6.dylib+0x1c285)
    #2 0x1070a1d10 in xtCreate (/usr/X11/lib/libXt.6.dylib+0x19d10)
    #3 0x1070a14ab in _XtCreateWidget (/usr/X11/lib/libXt.6.dylib+0x194ab)
    #4 0x1071368ea in _XtVaCreateWidget (/usr/X11/lib/libXt.6.dylib+0xae8ea)
    #5 0x107136bbc in XtVaCreateManagedWidget (/usr/X11/lib/libXt.6.dylib+0xaebbc)
    #6 0x106c92900 in main (/usr/local/karma/bin/kvis+0x100001900)
    #7 0x106c92713 in start (/usr/local/karma/bin/kvis+0x100001713)
    #8 0x0  (<unknown module>)

AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV (/usr/local/karma/lib/libkarmawidgets.1.7.20.dylib+0x1e014) in _ImageDisplay_Initialise

Downgrading to 2.7.8 fixed the issue, so it must be something thats changed since then.

Tim Davis
Comment 1 Misty De Meo 2016-07-04 01:45:14 UTC
I've also had reports of this happening with wine using 2.7.9 and 2.7.10 beta 2. It appears these releases were built with address sanitization enabled.

wine, itself built without asan, fails like this at startup: https://github.com/Homebrew/homebrew-core/files/338776/winefail.txt It works fine with asan disabled. For more context, here's the Homebrew issue for the wine failures: https://github.com/Homebrew/homebrew-core/issues/2481
Comment 2 Misty De Meo 2016-07-04 01:49:11 UTC
Sorry, by "with asan disabled" I mean "with X11 disabled".
Comment 3 Jeremy Huddleston Sequoia 2016-07-04 07:17:02 UTC

*** This bug has been marked as a duplicate of bug 96292 ***
Comment 4 Jeremy Huddleston Sequoia 2016-07-04 07:18:23 UTC
The issue with wine is a completely different issue.  Please don't confuse them.

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.