Login  •  Register


The time is now: Mon Jul 06, 2020 9:24 am

Emaculation wiki  •  Delete all board cookies



Post new topic  Reply to topic Page 1 of 1 [ 13 posts ]
Print view Previous topic  |  Next topic
Author Message
PostPosted: Sat Dec 07, 2019 10:20 pm 
Offline
Forum All-Star
User avatar

Joined: Fri Nov 27, 2009 5:11 am
Posts: 2978
Location: Emaculation.com
Hi all,
I've got the following issue with the December 4 build of BII:

Quote:
/Applications/BasiliskII.app/Contents/MacOS/BasiliskII
Basilisk II V1.1 by Christian Bauer et al.
Reading ROM file...
Using SDL/coreaudio audio output
Using SDL_Renderer driver: metal
Caught SIGSEGV at address 0x110398ff5
D0: 00000000 D1: 000009e4 D2: 00000fe0 D3: 000009f0
D4: 000005f0 D5: 01400000 D6: 00000000 D7: 00a0fb01
A0: 000021c4 A1: 00000000 A2: 000021c4 A3: ff44f000
A4: 00001f4c A5: 00a0fd90 A6: 00002000 A7: 00a0fae2
USP=00000000 ISP=00a0fae2 MSP=00000000 VBR=00000000
T=00 S=1 M=0 X=0 N=0 Z=1 V=0 C=0 IMASK=0
FP0: nan FP1: nan FP2: nan FP3: nan
FP4: nan FP5: nan FP6: nan FP7: nan
N=0 Z=0 I=0 NAN=0
0140e90e: 175f fff5 4cdf 0f7e 4e75 MOVE.B (A7)+,(A3,$fff5) == $ff44eff5
next PC: 0140e912


This happens right after the ROM check.

With the July 11 version and the same config file, I get:

Quote:
Basilisk II V1.1 by Christian Bauer et al.
Reading ROM file...
Using SDL/coreaudio audio output
Using SDL_Renderer driver: opengl


and then it runs Mac OS 7.5.1 properly.

Anyone know what could be causing this segmentation fault?

As a comparison, the new build of SheepShaver ran without a hitch:

Quote:
SheepShaver V2.5 by Christian Bauer and Mar"c" Hellwig
Reading ROM file...
Using SDL/coreaudio audio output
Using SDL_Renderer driver: metal
Detected CPU features: MMX SSE SSE2 SSE3 SSSE3
PowerPC CPU emulator by Gwenole Beauchesne
WARNING: Unknown DiskStatus(6)


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Sat Dec 07, 2019 10:29 pm 
Offline
Forum All-Star
User avatar

Joined: Fri Nov 27, 2009 5:11 am
Posts: 2978
Location: Emaculation.com
Well, I'll reply to my own topic for anyone else who has this issue.

I had

ether etherhelper/tap0/bridge0/en0

and changing it to

ether slirp

did the trick. Interesting error to throw for the tap interface failing to come up correctly. Also interesting that this failure didn't happen in the July build, but happened in this one.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Sat Dec 07, 2019 10:53 pm 
Offline
Expert User
User avatar

Joined: Fri Feb 13, 2004 8:59 am
Posts: 4900
Location: Sittard, The Netherlands
Hi

Did you run Dsumorok's Appletalk-enabling build from here?
viewtopic.php?f=6&t=8067

I believe that preference only applies to builds from his source.

Best,
Cat_7


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Sat Dec 07, 2019 11:23 pm 
Offline
Forum All-Star
User avatar

Joined: Fri Nov 27, 2009 5:11 am
Posts: 2978
Location: Emaculation.com
Ah! That would explain it :) I did use that build years ago, and I guess I never bothered to update my prefs. Funny that all my prefs files just silently ignored it up until this build where I got a segfault.

I wonder if kanjitalk755 would be willing to roll those additions into his repo?


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Sun Dec 08, 2019 9:50 am 
Offline
Space Cadet
User avatar

Joined: Tue Dec 03, 2019 9:26 pm
Posts: 8
Hi all,
I'm new here. Been a long time lurker though.

I had the exact same issue with the December Build. For me it was the jit compiler that was causing it... The October build didn't have this problem.


Last edited by Ronald P. Regensburg on Sun Dec 08, 2019 3:05 pm, edited 1 time in total.
 


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Sun Dec 08, 2019 11:59 am 
Offline
Expert User
User avatar

Joined: Thu Feb 09, 2006 10:24 pm
Posts: 6016
Location: Amsterdam, Netherlands
BadGoldEagle wrote:
I had the exact same issue with the December Build. For me it was the jit compiler that was causing it... The October build didn't have this problem.
The previous 2.5 (SDL2 port) builds had JIT disabled because it was too unstable. In this latest build JIT is again available, but still incomplete and not very stable. Best keep JIT disabled, in the prefs file:
Code:
jit false


Last edited by Ronald P. Regensburg on Sun Dec 08, 2019 3:06 pm, edited 1 time in total.
 


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Sun Dec 08, 2019 3:29 pm 
Offline
Expert User
User avatar

Joined: Thu Feb 09, 2006 10:24 pm
Posts: 6016
Location: Amsterdam, Netherlands
I don't think this issue is related to having JIT enabled or to having ether set to etherhelper/tap0/bridge0/en0

I have ether set to slirp and jit set to false.
When l try to launch BasiliskII in the Finder, it often fails a couple of times before BasiliskII starts and runs normally. The icon bounces once or twice in the Dock and then it stops.

When I try to launch BasiliskII using Terminal, it failed always so far. Again the icon bounces once or twice in the Dock and then it stops. The output in Terminal is the same as reported above:

Code:
/Applications/BasiliskII/BasiliskII.app/Contents/MacOS/BasiliskII
Basilisk II V1.1 by Christian Bauer et al.
WARNING: Unknown preferences keyword 'dsp'
WARNING: Unknown preferences keyword 'mixer'
WARNING: Unknown preferences keyword 'ignoresegv'
Reading ROM file...
Using SDL/coreaudio audio output
Using SDL_Renderer driver: metal
Caught SIGSEGV at address 0x10b8d1ff5
D0: 00000000 D1: 00000b24 D2: 00001380 D3: 00000b30
D4: 00000850 D5: 10000000 D6: 00000000 D7: 0800fb01
A0: 000021c4 A1: 00000000 A2: 000021c4 A3: fe478000
A4: 00001f4c A5: 0800fd90 A6: 00002000 A7: 0800fae2
USP=00000000 ISP=0800fae2 MSP=00000000 VBR=00000000
T=00 S=1 M=0 X=0 N=0 Z=1 V=0 C=0 IMASK=0
FP0: nan FP1: nan FP2: nan FP3: nan
FP4: nan FP5: nan FP6: nan FP7: nan
N=0 Z=0 I=0 NAN=0
1000e90e: 175f fff5 4cdf 0f7e 4e75 MOVE.B (A7)+,(A3,$fff5) == $fe477ff5
next PC: 1000e912


(The warnings about unknown prefs keywords are irrelevant here. Those are settings not yet implemented. It has been so in previous builds.)


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Mon Dec 09, 2019 1:56 am 
Offline
Granny Smith

Joined: Thu Nov 09, 2017 12:06 pm
Posts: 134
I have reverted my fork since the JIT compiler is unstable (even if disabled by pref).
Try my latest source.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Mon Dec 09, 2019 12:17 pm 
Offline
Expert User
User avatar

Joined: Thu Feb 09, 2006 10:24 pm
Posts: 6016
Location: Amsterdam, Netherlands
I will post a new BasiliskII build from the latest source soon.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Mon Dec 09, 2019 8:52 pm 
Offline
Expert User
User avatar

Joined: Thu Feb 09, 2006 10:24 pm
Posts: 6016
Location: Amsterdam, Netherlands
A new 9 December 2019 build is here: https://www.emaculation.com/basilisk/Ba ... 191209.zip

The instability issue appears to be solved. JIT is again disabled in the source code. According to kanjitalk755, the instability caused by the JIT code could not be fully prevented by disabling JIT in the prefs setting.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Wed Dec 11, 2019 6:23 pm 
Offline
Tinkerer
User avatar

Joined: Thu Apr 06, 2017 9:32 am
Posts: 77
Dear all,

Same applied to me, the new version from 9th of December did the trick!
But that might work for an already existing installation, a brand new setup from scratch failed on my side. I can‘t make use of the.DiskTools to format a new drive. The System 8 Disk Tools were not accepted by the new setuo.

Any idea to get this solved?

If I use the original tools, I might loose the shared UNIX folder.

Best,
Knuddelmac!


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Wed Dec 11, 2019 7:38 pm 
Offline
Expert User
User avatar

Joined: Thu Feb 09, 2006 10:24 pm
Posts: 6016
Location: Amsterdam, Netherlands
KnuddlMac wrote:
The System 8 Disk Tools were not accepted by the new setuo.
See my reply in the other topic.

Quote:
If I use the original tools, I might loose the shared UNIX folder.
Why? How? What do you mean?


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Mon Dec 30, 2019 9:46 am 
Offline
Tinkerer
User avatar

Joined: Thu Apr 06, 2017 9:32 am
Posts: 77
Ronald P. Regensburg wrote:
Why? How? What do you mean?


Sorry my wrong thinking!

Now I understand: The Unix folder is just on file system level and represents the 'Shared Files'. - So nothing will be lost.

Right now I am struggling with tuntap support on Catalina. - But as good citizen I opened another post about this topic. :)


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


Who is online

Users browsing this forum: No registered users and 24 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