Hi Francis On Tuesday 14 June 2005 05:11 pm, francis klein wrote: > I have tested the newbsdsocket_emu with Thor (the newsreader). > > On the G5 (Panther) > I get a few posts and the Amiga hang, the pointer freeze, but the > Emulation don't crash, i have to reboot (F11+R) > > I have tried with the 20050607 build just in case. i have > recuperated 1000+ posts without a problem. > > I have retried with the 20050614, same thing as the first time, hang > & freeze. > > But, I have failed to reproduce the problem with the G4 (Tiger). > Thor seem to be working fine with the newbsdsocket. > > Tomorrow i try to switch the configurations between the two > computers, just to be sure. > Maybe your are right for the stack magic stuff problems on the G5. > > Hope to make sens with my poor english. sorry for that. Okay. To summarize what you've written and to check that I understand you: The 'new' bsdsocket emulation (in 20050614) works okay on your G4/Tiger system, but doesn't on your G5/Panther system? I would guess that the stack-twiddling that the 'new' bsdsocket code does would be a problem on the G5, because, as far as I undersand it (and I'm fairly sure I do), the PowerPC architecture doesn't have 32-bit and 64-bit modes like, for instance, the AMD64 has. You can run 32-bit binaries transparently on a 64-bit chip - the problem is, as far as the stack magic code is concerned, a 64-bit PPC chip still uses 64-bit stack frames when running 32-bit code. So I don't think I can fix this at the moment, short of creating a 64-bit E-UAE executable (which I'm not even sure that I can do, since I'm still running 10.2 here). Possible solutions: 1) Provide a binary which uses the 'old' bsdsocket emulation. 2) Provide a PPC64 binary with a fixed 'new' bsdsocket emulation for G5 users. 3) Find another solution for getting the 'new' bsdsocket emulation which doesn't perform voodoo on the stack. You can probably see why I think the stack-magic stuff is evil. ;-) Anybody else got any bright ideas? Cheers, Rich