Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SheepShaver doesn't run in 64-bit mode on macOS 10.10+ #99

Open
vasi opened this issue Nov 2, 2016 · 10 comments
Open

SheepShaver doesn't run in 64-bit mode on macOS 10.10+ #99

vasi opened this issue Nov 2, 2016 · 10 comments

Comments

@vasi
Copy link
Contributor

vasi commented Nov 2, 2016

Yields "Killed: 9". LLDB reports "Malformed Mach-o file". Maybe lowmem is doing something wrong?

@chrisballinger
Copy link

lowmem definitely corrupts the binary, and it would only run if I disabled
it during the build steps, but I guess that breaks other things that depend
on whatever lowmem is doing.

On Wed, Nov 2, 2016 at 3:29 PM, Dave Vasilevsky notifications@github.com
wrote:

Yields "Killed: 9". LLDB reports "Malformed Mach-o file". Maybe lowmem is
doing something wrong?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#99, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAfqHy2V6rVVImKJLEIAnWhYbjqzrhggks5q6Q7HgaJpZM4Kn0s3
.

@asvitkine
Copy link
Collaborator

The 64-bit binaries work on older Mac OS X versions though. So it's
something that new versions of OS X reject.

On Wed, Nov 2, 2016 at 6:41 PM, Chris Ballinger notifications@github.com
wrote:

lowmem definitely corrupts the binary, and it would only run if I disabled
it during the build steps, but I guess that breaks other things that depend
on whatever lowmem is doing.

On Wed, Nov 2, 2016 at 3:29 PM, Dave Vasilevsky notifications@github.com
wrote:

Yields "Killed: 9". LLDB reports "Malformed Mach-o file". Maybe lowmem is
doing something wrong?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#99, or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AAfqHy2V6rVVImKJLEIAnWhYbjqzrhggks5q6Q7HgaJpZM4Kn0s3>
.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#99 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AABE8DrPSd2MPpLe6FkbR_hiYTjT_8jgks5q6RGzgaJpZM4Kn0s3
.

@asvitkine
Copy link
Collaborator

So some questions I have is whether it's related to what OS lowmem runs on
and what binaries are input to it.

For example, it could choke on binaries compiled by clang - but might work
fine on binaries compiled by GCC and Xcode 3.2 on 10.6.

Or it could be that lowmem running on 10.12 doesn't work as intended.

On Wed, Nov 2, 2016 at 9:29 PM, Alexei Svitkine alexei.svitkine@gmail.com
wrote:

The 64-bit binaries work on older Mac OS X versions though. So it's
something that new versions of OS X reject.

On Wed, Nov 2, 2016 at 6:41 PM, Chris Ballinger notifications@github.com
wrote:

lowmem definitely corrupts the binary, and it would only run if I disabled
it during the build steps, but I guess that breaks other things that
depend
on whatever lowmem is doing.

On Wed, Nov 2, 2016 at 3:29 PM, Dave Vasilevsky <notifications@github.com

wrote:

Yields "Killed: 9". LLDB reports "Malformed Mach-o file". Maybe lowmem
is
doing something wrong?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#99, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAfqHy2V6
rVVImKJLEIAnWhYbjqzrhggks5q6Q7HgaJpZM4Kn0s3>
.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#99 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AABE8DrPSd2MPpLe6FkbR_hiYTjT_8jgks5q6RGzgaJpZM4Kn0s3
.

@vasi
Copy link
Contributor Author

vasi commented Nov 3, 2016

I believe I compiled that version of SheepShaver on 10.6. Not 100% sure though.

@asvitkine
Copy link
Collaborator

Yep, I am able to reproduce those results now. It doesn't work on 10.11
either. Trying to debug what's wrong.

On Wed, Nov 2, 2016 at 9:36 PM, Dave Vasilevsky notifications@github.com
wrote:

I believe I compiled that version of SheepShaver on 10.6. Not 100% sure
though.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#99 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AABE8CH7KE-KNr_M9zcothK_CQNuq9qwks5q6Tq4gaJpZM4Kn0s3
.

@asvitkine
Copy link
Collaborator

Here's the reason:

http://stackoverflow.com/a/26696361

It's a protection for 64-bit binaries that was added in 10.10. Basically,
it disallows page zero from having anything the NONE permission. Not sure
if there's anything we can do to workaround it, other than having
SheepShaver not require that page zero is mapped.

On Wed, Nov 2, 2016 at 9:59 PM, Alexei Svitkine alexei.svitkine@gmail.com
wrote:

Yep, I am able to reproduce those results now. It doesn't work on 10.11
either. Trying to debug what's wrong.

On Wed, Nov 2, 2016 at 9:36 PM, Dave Vasilevsky notifications@github.com
wrote:

I believe I compiled that version of SheepShaver on 10.6. Not 100% sure
though.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#99 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AABE8CH7KE-KNr_M9zcothK_CQNuq9qwks5q6Tq4gaJpZM4Kn0s3
.

@asvitkine
Copy link
Collaborator

(The other workaround obviously is continuing using the 32-bit version
which still supports having page zero with VM_PROT_ALL permissions.)

On Wed, Nov 2, 2016 at 10:09 PM, Alexei Svitkine alexei.svitkine@gmail.com
wrote:

Here's the reason:

http://stackoverflow.com/a/26696361

It's a protection for 64-bit binaries that was added in 10.10. Basically,
it disallows page zero from having anything the NONE permission. Not sure
if there's anything we can do to workaround it, other than having
SheepShaver not require that page zero is mapped.

On Wed, Nov 2, 2016 at 9:59 PM, Alexei Svitkine <alexei.svitkine@gmail.com

wrote:

Yep, I am able to reproduce those results now. It doesn't work on 10.11
either. Trying to debug what's wrong.

On Wed, Nov 2, 2016 at 9:36 PM, Dave Vasilevsky <notifications@github.com

wrote:

I believe I compiled that version of SheepShaver on 10.6. Not 100% sure
though.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#99 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AABE8CH7KE-KNr_M9zcothK_CQNuq9qwks5q6Tq4gaJpZM4Kn0s3
.

@lequeu
Copy link

lequeu commented Mar 9, 2018

I have v 2.4.20140201 Working . with OS 9.0 on Mac OSX 10.12.3.. With no issues so far. I did migrate the build from my 10.8.5 former machine
screen shot 2018-03-09 at 4 04 29 pm

@RonaldPR
Copy link

When you check Finder Info for the SheepShaver application you will see that the option "Open in 32-bit mode" is checked.

@lequeu
Copy link

lequeu commented Mar 10, 2018

Indeed. When checking the finder "Open in 32bit mode" IS checked.
screen shot 2018-03-10 at 7 53 11 am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants