Login  •  Register


The time is now: Sat Nov 17, 2018 4:25 am

Emaculation wiki  •  Delete all board cookies



Post new topic  Reply to topic Page 1 of 1 [ 6 posts ]
Print view Previous topic  |  Next topic
Author Message
PostPosted: Tue Sep 04, 2018 7:47 pm 
Offline
Space Cadet

Joined: Tue Sep 04, 2018 7:37 pm
Posts: 2
I have been running SheepShaver for years under Mac OS X 10.9.5. Last week I updated to 10.11.6. I also had to update to SheepShaver_UB_20140201.
The sole purpose for running SheepShaver is to run Gene 4.3.4. https://www.ics.uci.edu/~eppstein/gene/
When launching Gene and click in the file opening window that appears, SheepShaver(!) crashes.

Here is the start of one crash report:
Code:
Process:               SheepShaver [1591]
Path:                  /Classic/SheepShaver_UB_20140201.app/Contents/MacOS/SheepShaver
Identifier:            SheepShaver
Version:               2.4.20140201 (2.4)
Code Type:             X86 (Native)
Parent Process:        ??? [1]
Responsible:           SheepShaver [1591]
User ID:               501

Date/Time:             2018-09-04 21:26:02.128 +0200
OS Version:            Mac OS X 10.11.6 (15G22010)
Report Version:        11
Anonymous UUID:        CB50E5D0-356D-AB98-3C72-7D8F2D641D24


Time Awake Since Boot: 54000 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:
abort() called

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib           0x95312572 __pthread_kill + 10
1   libsystem_pthread.dylib          0x9cfa0654 pthread_kill + 101
2   libsystem_c.dylib                0x9523ac38 abort + 156
3   SheepShaver                      0x780ad387 powerpc_cpu::execute_illegal(unsigned int) + 87
4   ???                              0x2a075eee 0 + 705126126




Here is the start of another crash report:
Code:
Process:               SheepShaver [1563]
Path:                  /Classic/SheepShaver_UB_20140201.app/Contents/MacOS/SheepShaver
Identifier:            SheepShaver
Version:               2.4.20140201 (2.4)
Code Type:             X86 (Native)
Parent Process:        ??? [1]
Responsible:           SheepShaver [1563]
User ID:               501

Date/Time:             2018-09-04 21:25:19.671 +0200
OS Version:            Mac OS X 10.11.6 (15G22010)
Report Version:        11
Anonymous UUID:        CB50E5D0-356D-AB98-3C72-7D8F2D641D24


Time Awake Since Boot: 54000 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000051a30100
Exception Note:        EXC_CORPSE_NOTIFY

VM Regions Near 0x51a30100:
    mapped file            000000002be31000-000000002d4f7000 [ 22.8M] r--/r-x SM=ALI  b
-->
    VM_ALLOCATE            0000000060000000-0000000060040000 [  256K] rw-/rwx SM=ZER 

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   SheepShaver                      0x780a0f80 powerpc_cpu::compile_block(unsigned int) + 240
1   SheepShaver                      0x780d1fdd powerpc_cpu::execute(unsigned int) + 1277
2   SheepShaver                      0x780d4efa emul_ppc(unsigned int) + 26
3   SheepShaver                      0x7808ab4a SDL_main + 2954
4   SheepShaver                      0x78072fa2 -[SDLMain applicationDidFinishLaunching:] + 66
5   com.apple.Foundation             0x9e2954d2 __57-[NSNotificationCenter addObserver:selector:name:object:]_block_invoke_2 + 50
6   com.apple.CoreFoundation         0x972ece14 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 20
7   com.apple.CoreFoundation         0x972ecd9b ___CFXRegistrationPost_block_invoke + 75
8   com.apple.CoreFoundation         0x972ecd0c _CFXRegistrationPost + 460
9   com.apple.CoreFoundation         0x972eca46 ___CFXNotificationPost_block_invoke + 54
10  com.apple.CoreFoundation         0x972a6393 -[_CFXNotificationRegistrar find:object:observer:enumerator:] + 1715
11  com.apple.CoreFoundation         0x972a55b2 _CFXNotificationPost + 626
12  com.apple.Foundation             0x9e2475e4 -[NSNotificationCenter postNotificationName:object:userInfo:] + 92
13  com.apple.AppKit                 0x993b0794 -[NSApplication _postDidFinishNotification] + 436
14  com.apple.AppKit                 0x993b0442 -[NSApplication _sendFinishLaunchingNotification] + 249
15  com.apple.AppKit                 0x9925a626 -[NSApplication(NSAppleEventHandling) _handleAEOpenEvent:] + 783
16  com.apple.AppKit                 0x99259f7b -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 291
17  libobjc.A.dylib                  0x9c33fdb2 -[NSObject performSelector:withObject:withObject:] + 84
18  com.apple.Foundation             0x9e298db0 __76-[NSAppleEventManager setEventHandler:andSelector:forEventClass:andEventID:]_block_invoke + 118
19  com.apple.Foundation             0x9e298907 -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 451
20  com.apple.Foundation             0x9e298702 _NSAppleEventManagerGenericHandler + 211
21  com.apple.AE                     0x9a7b9281 aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned long, unsigned char*) + 595
22  com.apple.AE                     0x9a78aca5 dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 44
23  com.apple.AE                     0x9a78abb8 aeProcessAppleEvent + 299
24  com.apple.HIToolbox              0x9deb585a AEProcessAppleEvent + 55
25  com.apple.AppKit                 0x99255834 _DPSNextEvent + 2415
26  com.apple.AppKit                 0x9925485b -[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1057
27  com.apple.AppKit                 0x99254432 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 121
28  com.apple.AppKit                 0x99247b47 -[NSApplication run] + 1063
29  SheepShaver                      0x7807368c main + 1436
30  SheepShaver                      0x78055686 _start + 216
31  SheepShaver                      0x780555ad start + 41


Any advice?

Thanks in advance.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Tue Sep 04, 2018 9:12 pm 
Offline
Forum All-Star

Joined: Wed Nov 11, 2009 5:47 pm
Posts: 1156
Location: Germany
You may want to try the latest Sheepshaver build 2.5 from 21. June 2018.
Both Gene 4.2.1 and 4.3.4 do open the Example.gene fine on my side, macOS Sierra, SheepShaver MacOS 8.6, OldWorldROM.


Last edited by 24bit on Wed Sep 05, 2018 9:36 am, edited 1 time in total.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Wed Sep 05, 2018 7:31 am 
Offline
Expert User
User avatar

Joined: Thu Feb 09, 2006 10:24 pm
Posts: 5183
Location: Amsterdam, Netherlands
24bit wrote:
You may want to try the latest Sheepshaver build 2.5 from 21. June 2018..

Best try the July 11 2018 2.5 version build, it mostly solves a caps lock issue when SheepShaver is launched with caps lock on that existed in the previous 2.5 version builds. (A July 12 build also existed that tried to further solve the caps lock issue, but instead made it worse again).
http://ronaldpr.home.xs4all.nl/sheepsha ... 1_test.zip

Probably more important: Make sure that in SheepShaver Preferences > Miscellaneous the option "Ignore Illegal Memory Accesses" is enabled.


Last edited by Ronald P. Regensburg on Wed Sep 05, 2018 9:24 am, edited 3 times in total.
I wrote June where it should have been July. Corrected that.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Wed Sep 05, 2018 9:39 am 
Offline
Forum All-Star

Joined: Wed Nov 11, 2009 5:47 pm
Posts: 1156
Location: Germany
Thanks Ronald!
Always a good idea to use your most up to date build.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Wed Sep 05, 2018 3:30 pm 
Offline
Space Cadet

Joined: Tue Sep 04, 2018 7:37 pm
Posts: 2
Hmmm. I thought my version was the latest (stable) one.

The last build I found was from June 8, 2018 and it worked just fine.
Then I saw Ronald's post about an even later version.

And thanks for the tip about ignoring illegal memory access. It is now checked.

Thank you both. I'm now happy again.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Mon Oct 08, 2018 2:54 am 
Offline
Space Cadet

Joined: Mon Oct 08, 2018 2:40 am
Posts: 1
Hi and thanks. I just wanted to note that I've been having this exact problem (Gene 4.3.4 etc.), and the June 8 build resolved it.

"Ignore Illegal Memory Accesses" was already checked, so not that (in my case anyway).


Top
 Profile  
Reply with quote Post a reply  
Display posts from previous:  Sort by  
Post new topic  Reply to topic Page 1 of 1 [ 6 posts ]


Who is online

Users browsing this forum: Google [Bot] and 5 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
 

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group