ASan issue on macOS 10.12 - Wine, running winbox.exe [EDIT: XQuartz 2.7.9-2.7.10_Beta2 ASan] #2481

AlexanderNeilson · 2016-06-29T03:26:29Z

Please follow the general troubleshooting steps first:

[yes] Ran brew update and retried your prior step?
[yes] Ran brew doctor, fixed as many issues as possible and retried your prior step? (Python installed to non standard location - for python development - not removed)

You can erase any parts of this template not applicable to your Issue.

Bug reports:

My particular builds of Wine --devel under macOS 10.12 appears to invoke / include address sanitizer in the build which causes failures to execute apps. Mistydemeo was unable to reproduce so separated from issue: 1597 Earlier discussion

Gist-Logs Output

Looks to be a local issue if it can't be reproduced by others, AFAIK there is no relationship to python at any part of this installation so my location of python shouldn't have any effect.

To try resolve this I have blown away my whole xcode installation and followed all instructions for removal of Homebrew. Then reinstalled xcode-beta and homebrew as if a new install. New install was then attempted with wine --devel as the only install (plus obviously dependencies).

I am thinking my next step may need to have a full wipe and reinstall of the system from base to eliminate the effect and rebuild my system around whats there, if anyone can provide some insight however into what could be causing this to happen or that I could try investigate.

The text was updated successfully, but these errors were encountered:

mistydemeo · 2016-06-29T03:32:10Z

Can you show me the output of the following commands?

otool -L /usr/local/opt/wine/lib/libwine.1.dylib
otool -L /usr/local/opt/wine/bin/wine.bin

AlexanderNeilson · 2016-06-29T03:45:53Z

Atlantis:Git alexander$ otool -L /usr/local/opt/wine/lib/libwine.1.dylib
/usr/local/opt/wine/lib/libwine.1.dylib:
    /usr/local/opt/wine/lib/libwine.1.dylib (compatibility version 1.0.0, current version 1.0.0)
    /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1333.20.0)
    /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (compatibility version 1.0.0, current version 763.1.0)
    /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1237.0.0)
Atlantis:Git alexander$

Atlantis:Git alexander$ otool -L /usr/local/opt/wine/bin/wine.bin
/usr/local/opt/wine/bin/wine.bin:
    @rpath/libwine.1.dylib (compatibility version 1.0.0, current version 1.0.0)
    /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1237.0.0)
Atlantis:Git alexander$

mistydemeo · 2016-06-29T07:00:50Z

And just for completeness, can you include in this issue the full output you get when it fails?

AlexanderNeilson · 2016-06-29T07:56:23Z

winefail.txt

Hopefully this can help with any guidance / testing?

Regards
Alexander

AlexanderNeilson · 2016-06-30T12:38:03Z

Hi Team

I went back and wiped the entire machine, fresh install from fresh download on macOS 10.12.

After the install I completed normal user setup, installed XQuartz 2.7.10 Beta 2, install homebrew (allowing it to install command line tools directly), then brew install wine --devel, brew install winetricks.

Then I downloaded a fresh copy of winbox.exe and wine ~/winbox.exe (downloaded into my home directory).

I am still seeing the same memory (address sanitiser) errors. I am starting to wonder if there could be either a hardware issue or a problem with the small amount of ram in the MacBook Air 13".

Is anyone else experiencing this as an issue with anything they try?

New Gist-Logs
Build Process - BuildWineClean.txt
What happens when I run winbox.exe - RebuildFailWine.txt

Alexanders-MacBook-Air:~ alexander$ otool -L /usr/local/opt/wine/lib/libwine.1.dylib
/usr/local/opt/wine/lib/libwine.1.dylib:
    /usr/local/opt/wine/lib/libwine.1.dylib (compatibility version 1.0.0, current version 1.0.0)
    /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1333.20.0)
    /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (compatibility version 1.0.0, current version 763.1.0)
    /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1237.0.0)
Alexanders-MacBook-Air:~ alexander$

Alexanders-MacBook-Air:~ alexander$ otool -L /usr/local/opt/wine/bin/wine.bin
/usr/local/opt/wine/bin/wine.bin:
    @rpath/libwine.1.dylib (compatibility version 1.0.0, current version 1.0.0)
    /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1237.0.0)
Alexanders-MacBook-Air:~ alexander$

Any guidance to locating these faults or providing further helpful information that would be much appreciated.

Regards
Alexander

mistydemeo · 2016-07-01T00:16:25Z

Do you mind providing the output of env? Feel free to redact anything. I'm wondering if there might be environment variables influencing this.

AlexanderNeilson · 2016-07-01T00:47:07Z

I will go back to 10.12 as soon as I can again, I am currently rebuilding the machine as 10.11 fresh and untouched so I can confirm that its definitely related to something in my 10.12 and not something like a bug in the latest XQuartz (also this machine is my main road machine so I have been taking my MBP to the field with me).

I may also get my MBA back on track and try the same setup on the MBP and see what is different.

Thank you again for all the time you putting into helping something that you can't reproduce.

Regards
Alexander

mheaton228 · 2016-07-01T00:59:55Z

I think I'm having the same issue. There's something with the ASan that keeps buggering up with installing any .exe I'm trying after a clean install of 10.12. I was able to get Wine and Winetricks installed but with any other program I am getting:

==70931==Shadow memory range interleaves with an existing memory mapping. ASan cannot proceed correctly. ABORTING.
==70931==ASan shadow was supposed to be located in the [0x1ffff000-0x3fffffff] range.

It also referenced this thread. I can show you what's in my env if you'd like.

AlexanderNeilson · 2016-07-01T01:10:01Z

Hi mheaton228

That does look like the same thing, If you can provide your full output when you run the apps, the gist-logs, etc as above just to validate. Also if you can send in your env then that may help.

As I test last night I tried regedit in my wine and it threw the same error for me as my winbox so it seems wine wide.

Can you also confirm please what kind of machine you are running it on? how much ram? what model mac? and what version of XQuartz? just to try find a commonality.

Regards
Alexander

mistydemeo · 2016-07-01T01:43:48Z

I just noticed this in your brew --config:

X11: 2.7.10_beta2 => /opt/X11

Whereas I installed the stable release:

X11: 2.7.9 => /opt/X11

Can one of you downgrade to 2.7.9 and see if that resolves your issue?

AlexanderNeilson · 2016-07-01T02:11:10Z

@mheaton228

Can you confirm if you are on 2.7.10_beta2?

I have been using that and I am currently in the build phase for my wine on 10.11 with 2.7.10_beta2. If this fails we may have our common factor and be able to zero in on a root cause.

If this dies then I will go back up to 10.12 and try with 2.7.9.

Regards
Alexander

mistydemeo · 2016-07-01T02:14:42Z

I'm seeing a report on the XQuartz tracker that suggests that 2.7.10 (and maybe some builds of 2.7.9) are built with ASan, leading to bugs like this one: https://bugs.freedesktop.org/show_bug.cgi?id=96666

mheaton228 · 2016-07-01T03:02:52Z

I wasn't able to install Wine at all until I upgraded to the 2.7.10_beta2 and XCode 8 beta, but I did the XQuartz upgrade before I did the XCode upgrade.

Here's the stuff requested:

AlexanderNeilson · 2016-07-01T03:34:11Z

I can confirm I see the same failure on 10.11 with 2.7.10_beta2

Tonight when I get home from work I will install 10.12 again and then install wine without XQuartz (as it should be only an optional not a requirement) then I can also try it with 2.7.8, 2.7.9, and see if I can come up with some clear advice for users.

Regards
Alexander

mistydemeo · 2016-07-01T06:49:27Z

I just realized that, while I have XQuartz 2.7.9 installed, I've been running wine using the Mac driver. You appear to be using the X driver, yes? Does this occur using the Mac driver?

AlexanderNeilson · 2016-07-01T07:21:43Z

My system is building from scratch again now so hopefully results without XQuartz within an hour or so.

I understood even with XQuartz installed that the system would build both available but still use Mac driver by default. But maybe not. So I will try it clean now and see how that goes.

Regards
Alexander

sidneys · 2016-07-02T06:09:10Z

I am having the a similar issue on El Capitan using the XCode 8 Beta: Cannot install Wine at all at the moment. Console message pointed me to this issue...

AlexanderNeilson · 2016-07-02T07:13:14Z

Hi team.

It looks like this can be confirmed as a problem linked to XQuartz.

I can build under 10.12 without XQuartz (note you need to add --without-x11 to your install command) and have my wine apps execute.

I haven't tried it built against XQuartz 2.7.8 yet but I can try that but if people could remove it and then rebuild without linking to X11 then we may be able to advise people or look at varying install if these versions are detected.

Regards
Alexander

mistydemeo · 2016-07-04T01:46:29Z

I can't seem to reproduce on 10.11 with XQuartz 2.7.9, but I'm pretty confident about what the issue is now.

mistydemeo · 2016-07-04T06:02:32Z

Can someone who has XQuartz 2.7.9 installed who didn't previously have 2.7.10 beta installed check if there's an /opt/X11/lib/asan directory? I do not have that, with 2.7.9 installed over 2.7.8.

This thread confirms that the beta releases of XQuartz use address sanitization for debug purposes: https://lists.macosforge.org/pipermail/xquartz-dev/2016-May/003957.html The implication is that the stable releases aren't intended to.

mistydemeo · 2016-07-04T06:06:08Z

@sidneys I don't think your issue is related; can you please open a new issue with the debug output specified in the troublshooting page? Thanks!

AlexanderNeilson · 2016-07-04T06:35:45Z

I have just installed 2.7.9 onto my MBP (Still on 10.11.6).

Was previously running 2.7.8 and confirmed the folder was not in place at that point.

My install of 2.7.9 comes off a fresh download taken from the project homepage main link.

After the installation I am not seeing /opt/X11/lib/asan on my drive.

Regards
Alexander

jeremyhu · 2016-07-04T07:19:54Z

wine is not compatible with asan. See https://llvm.org/bugs/show_bug.cgi?id=25466

jeremyhu · 2016-07-04T07:20:34Z

@mistydemeo ASan is only used for beta builds. ASan was not used for 2.7.9_rc* and 2.7.9.

mistydemeo · 2016-07-04T07:29:39Z

@jeremyhu Perfect, thanks for the confirmation.

Beta versions of XQuartz have address sanitization enabled, which breaks some software at runtime, including wine. Closes Homebrew/homebrew-core#2481.

mistydemeo · 2016-07-06T07:22:48Z

Added a warning about beta XQuartz releases.

Beta versions of XQuartz have address sanitization enabled, which breaks some software at runtime, including wine. Closes Homebrew/homebrew-core#2481. Closes Homebrew#459. Signed-off-by: Misty De Meo <mistydemeo@github.com>

DomT4 added the 10.12 Sierra is specifically affected label Jun 29, 2016

AlexanderNeilson changed the title ~~ASan issue on macOS 10.12 - Wine, running winbox.exe~~ ASan issue on macOS 10.12 - Wine, running winbox.exe [EDIT: XQuartz 2.7.9-2.7.10_Beta2 ASan] Jul 2, 2016

mistydemeo added a commit to mistydemeo/brew that referenced this issue Jul 6, 2016

doctor: check for beta XQuartz releases

ee7877d

Beta versions of XQuartz have address sanitization enabled, which breaks some software at runtime, including wine. Closes Homebrew/homebrew-core#2481.

mistydemeo closed this as completed in Homebrew/brew@ca005cb Jul 6, 2016

Homebrew locked and limited conversation to collaborators May 4, 2018

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

ASan issue on macOS 10.12 - Wine, running winbox.exe [EDIT: XQuartz 2.7.9-2.7.10_Beta2 ASan] #2481

ASan issue on macOS 10.12 - Wine, running winbox.exe [EDIT: XQuartz 2.7.9-2.7.10_Beta2 ASan] #2481

AlexanderNeilson commented Jun 29, 2016

mistydemeo commented Jun 29, 2016

AlexanderNeilson commented Jun 29, 2016

mistydemeo commented Jun 29, 2016

AlexanderNeilson commented Jun 29, 2016

AlexanderNeilson commented Jun 30, 2016

mistydemeo commented Jul 1, 2016

AlexanderNeilson commented Jul 1, 2016

mheaton228 commented Jul 1, 2016

AlexanderNeilson commented Jul 1, 2016

mistydemeo commented Jul 1, 2016

AlexanderNeilson commented Jul 1, 2016

mistydemeo commented Jul 1, 2016

mheaton228 commented Jul 1, 2016

AlexanderNeilson commented Jul 1, 2016

mistydemeo commented Jul 1, 2016

AlexanderNeilson commented Jul 1, 2016

sidneys commented Jul 2, 2016

AlexanderNeilson commented Jul 2, 2016

mistydemeo commented Jul 4, 2016

mistydemeo commented Jul 4, 2016

mistydemeo commented Jul 4, 2016

AlexanderNeilson commented Jul 4, 2016

jeremyhu commented Jul 4, 2016

jeremyhu commented Jul 4, 2016

mistydemeo commented Jul 4, 2016

mistydemeo commented Jul 6, 2016

ASan issue on macOS 10.12 - Wine, running winbox.exe [EDIT: XQuartz 2.7.9-2.7.10_Beta2 ASan] #2481

ASan issue on macOS 10.12 - Wine, running winbox.exe [EDIT: XQuartz 2.7.9-2.7.10_Beta2 ASan] #2481

Comments

AlexanderNeilson commented Jun 29, 2016

Please follow the general troubleshooting steps first:

Bug reports:

mistydemeo commented Jun 29, 2016

AlexanderNeilson commented Jun 29, 2016

mistydemeo commented Jun 29, 2016

AlexanderNeilson commented Jun 29, 2016

AlexanderNeilson commented Jun 30, 2016

mistydemeo commented Jul 1, 2016

AlexanderNeilson commented Jul 1, 2016

mheaton228 commented Jul 1, 2016

AlexanderNeilson commented Jul 1, 2016

mistydemeo commented Jul 1, 2016

AlexanderNeilson commented Jul 1, 2016

mistydemeo commented Jul 1, 2016

mheaton228 commented Jul 1, 2016

AlexanderNeilson commented Jul 1, 2016

mistydemeo commented Jul 1, 2016

AlexanderNeilson commented Jul 1, 2016

sidneys commented Jul 2, 2016

AlexanderNeilson commented Jul 2, 2016

mistydemeo commented Jul 4, 2016

mistydemeo commented Jul 4, 2016

mistydemeo commented Jul 4, 2016

AlexanderNeilson commented Jul 4, 2016

jeremyhu commented Jul 4, 2016

jeremyhu commented Jul 4, 2016

mistydemeo commented Jul 4, 2016

mistydemeo commented Jul 6, 2016