Re: [B2-devel] SheepShaver on MacOS X issues

[Dara H. <dha...@ya...>]

--- Gwenole Beauchesne <gb...@di...> wrote:
> There was an old bug in video code that prevented to
> shutdown 
> completely. i.e. the window remained active.

Ah, ok...
> 
> > At this point, I'd just like to understand why
> > disabling esound makes booting fail... Otherwise
> I'm
> > happy that OS 7.6 works fine now!
> 
> You will probably want to use SDL. For MacOS X, I am
> confiugring 
> SheepShaver as follows:
> --enable-sdl-static --enable-sdl-video
> --enable-sdl-audio --without-gtk
> 
> The interesting thing to test is --enable-sdl-audio.
> Then, you can 
> check if you still get errors with the ESD backend
> through SDL as 
> follows: SDL_AUDIODRIVER=esd ./SheepShaver. 
> Otherwise, SDL uses the 
> SoundManager by default and this one works for me.

Okay, built as described above. Neither with
SDL_AUDIODRIVER=esd nor without do I hear any sound.
It does the usual start-booting, crash,
continue-booting routine.

Crashreporter gives me the usual "thread 0 crashed"
stuff...

Thread 0 Crashed:
0   ???                         0x00022f6c
catch_exception_raise + 0x1310
1   ???                         0x00023634
catch_exception_raise + 0x19d8
2   ???                         0x00023c34
catch_exception_raise + 0x1fd8
3   ???                         0x000241a0
catch_exception_raise + 0x2544
4   ???                         0x000054bc 0x3000 +
0x24bc
5   ???                         0x00029e80
catch_exception_raise + 0x8224
6   com.apple.Foundation        0x909f7184
_nsnote_callback + 0xb0
7   com.apple.CoreFoundation    0x901aa650
__CFXNotificationPost + 0x1b4
8   com.apple.CoreFoundation    0x901af060
_CFXNotificationPostNotification + 0x340
9   com.apple.Foundation        0x909f4fd0
-[NSNotificationCenter
postNotificationName:object:userInfo:] + 0x74
10  com.apple.AppKit            0x92ee37b8
-[NSApplication _postDidFinishNotification] + 0x70
11  com.apple.AppKit            0x92ee36a4
-[NSApplication _sendFinishLaunchingNotification] +
0x5c
12  com.apple.AppKit            0x92ee38d4
-[NSApplication(NSAppleEventHandling)
_handleCoreEvent:withReplyEvent:] + 0x78
13  com.apple.Foundation        0x90a4a544
-[NSAppleEventManager
dispatchRawAppleEvent:withRawReply:handlerRefCon:] +
0x164
14  com.apple.Foundation        0x90a50c6c
_NSAppleEventManagerGenericHandler + 0x78
15  com.apple.AE                0x9167ea68
aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned
long, unsigned char*) + 0xd0
16  com.apple.AE                0x916818b0
dispatchEventAndSendReply(AEDesc const*, AEDesc*) +
0x2c
17  com.apple.AE                0x9167eca8
aeProcessAppleEvent + 0x11c
18  com.apple.HIToolbox         0x928c47f4
AEProcessAppleEvent + 0x3c
19  com.apple.AppKit            0x92dd2c0c
_DPSNextEvent + 0x358
20  com.apple.AppKit            0x92de93b0
-[NSApplication
nextEventMatchingMask:untilDate:inMode:dequeue:] +
0x74
21  com.apple.AppKit            0x92dfd718
-[NSApplication run] + 0x21c
22  ???                         0x00029e08
catch_exception_raise + 0x81ac
23  ???                         0x0002a0cc
catch_exception_raise + 0x8470
24  ???                         0x00004810 0x3000 +
0x1810
25  ???                         0x00004684 0x3000 +
0x1684PPC Thread 

State:  srr0: 0x00022f6c srr1: 0x0000f930             
  vrsave: 0x00000000    cr: 0x82004228  xer:
0x00000007   lr: 0x00022f3c  ctr: 0x90008900    r0:
0x0000012e   r1: 0xbfffe5e0   r2: 0x00000000   r3:
0x0003e00c    r4: 0xe8b56f5d   r5: 0x00000198   r6:
0x00009858   r7: 0x0003e00c    r8: 0x00000000   r9:
0x006b5000  r10: 0x00000001  r11: 0x00086a68   r12:
0x000f4240  r13: 0x00000000  r14: 0x00000000  r15:
0x00000000   r16: 0x00074b90  r17: 0x00074b90  r18:
0x00074b90  r19: 0x00074b90   r20: 0x0008351c  r21:
0x0008351c  r22: 0x00086a68  r23: 0xbfffe630   r24:
0x00000000  r25: 0x00086a68  r26: 0x00000000  r27:
0xbfffe620   r28: 0x00086a68  r29: 0x0003e00c  r30:
0xe8b56f5d  r31: 0x00022f08

The code segment in question looks something like:

0x00022f54 <catch_exception_raise+4856>:        mr    
 r11,r22
0x00022f58 <catch_exception_raise+4860>:        li    
 r8,0
0x00022f5c <catch_exception_raise+4864>:        lwz   
 r2,8(r11)
0x00022f60 <catch_exception_raise+4868>:        lwz   
 r9,0(r11)
0x00022f64 <catch_exception_raise+4872>:        mullw 
 r2,r10,r2
0x00022f68 <catch_exception_raise+4876>:        addi  
 r10,r10,1
0x00022f6c <catch_exception_raise+4880>:        stbx  
 r8,r9,r2
_________________________________________________________________
0x00022f70 <catch_exception_raise+4884>:        lwz   
 r0,16(r11)
0x00022f74 <catch_exception_raise+4888>:        cmplw 
 cr7,r10,r0


Do you think that this is probably a MacOS bug at this
point? If so, is it likely to be fixable? I can live
with it, but it is somewhat annoying...

On a completely different note, how hard would
something like tun-based ethernet be to implement for
OS X?

Cheers,

Dara

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com