Hello, I also see the crash on PPC G4, both on 10.5.8 and 10.4.11. I am still not understand what has changed in the Mono runtime that makes the application crash. I googled a bit on the SIGILL signal: it is often releated to missing processor op-code. But if the problem shows on the three PPC generations, it cannot be a mis-building of the framework. I don't see any issue in the native library, as only simple types are passed in and out. I will continue my testing on these platforms.
Regards, Laurent Etiemble. 2009/11/12 Anthony Bowker <[email protected]>: > Testing summary: > > With test monobjc and Mono 2.6 Preview 1, bundled as universal: > On OS 10.4.11 (PPC G3), crash - see attached > On OS 10.5.8 (PPC G5), crash - see attached > On OS 10.6.2 (Intel), works ok > > With test monobjc and Mono 2.4.2.3, bundled as universal: > On OS 10.4.11 (PPC G3), works ok > On OS 10.5.8 (PPC G5), works ok > On OS 10.6.2 (Intel), works ok > > So what's wrong with Mono 2.6? > > Regards, > Anthony > > -----Original Message----- > From: Anthony Bowker [mailto:[email protected]] > Sent: Thursday, November 12, 2009 10:56 AM > To: 'Laurent Etiemble' > Subject: RE: [[email protected]] Snow Leopard support: call for > testing > > Hi Laurent, > > Yes, of course: > - does your application have multi-thread code ? It's primarily a UI app > running most of the code on the UI thread. However there are some non-UI > worker threads. > - if so, does it relies on NSThread or .Net Thread ? .Net Threads > - if so, does it creates or reuse a lot of thread (with a ThreadPool) ? No. > > When I tested I didn't exercise the worker threads much as I focused on the > UI. I will do some more testing with the worker threads. > > Also if it matters I am using OS 10.6.2. > > And I will also test the app (with the test monobjc) on PPC 10.5 and PPC > 10.4 > > Regards, > Anthony > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Laurent Etiemble > Sent: Thursday, November 12, 2009 2:16 AM > To: Anthony Bowker > Subject: Re: [[email protected]] Snow Leopard support: call for > testing > > Hello, > > Good news. A few more questions, if you don't mind: > - does your application have multi-thread code ? > - if so, does it relies on NSThread or .Net Thread ? > - if so, does it creates or reuse a lot of thread (with a ThreadPool) ? > > Regads, Laurent Etiemble. > > 2009/11/12 Anthony Bowker <[email protected]>: >> I have done some brief testing today, will do some more over the coming >> days: >> >> - the platform you are testing on (OS and Processor): Mac OS 10.6, Intel >> (2.4GHz Core 2 Duo) >> - the Mono version you are testing with: 2.6 Preview 1 >> - the kind of application you are testing: Windowed application with > several >> windows, icons, controls (owner drawn and OpenGL) >> - the result (work or crash): Works for > 30 minutes, whereas on monobjc >> 413, it would crash after a few minutes. >> >> My app is bundled as a native bundle. I have some custom code to add > dllmap >> entries into the configuration, so manually added an entry for >> libmonobjc.2.dylib. >> >> Incredible thank you for crafting this fix. It's really nice that there's >> not need to make changes to the mono runtime. >> >> Regards, >> Anthony >> >> -----Original Message----- >> From: Anthony Bowker [mailto:[email protected]] >> Sent: Wednesday, November 11, 2009 10:37 AM >> To: [email protected] >> Subject: RE: [[email protected]] Snow Leopard support: call for >> testing >> >> This sounds great! I will get testing today! >> >> Thanks, >> Anthony >> >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] On >> Behalf Of Laurent Etiemble >> Sent: Wednesday, November 11, 2009 10:33 AM >> To: Monobjc User List; Monobjc Devel List >> Subject: [[email protected]] Snow Leopard support: call for testing >> >> Hello, >> >> I have finally come to a solution regarding the Snow Leopard support: >> I have introduced a native library into the bridge to avoid the >> reported crash on Mac OS X 10.6 [1]. After reviewing all the >> feebacks[2][3], I came to the conclusion that a native library was the >> only solution to: >> - avoid the native/managed cross-calls when a thread exists and >> dealloc its exit notification >> - avoid the Mono runtime hacking (the Mono team is not really for it) >> >> The preview of the new release of the bridge is available for >> download: http://downloads.monobjc.net/Monobjc-2.0.436.0.tar.gz >> >> Here are some noticeable points: >> - the bridge now requires two shared libraries: libmonobjc.1.dylib and >> libmonobjc.2.dylib (They are used for each version of the Objective-C >> runtime). You have to put them in the MacOS folder of the application >> bundle. Refer to the samples applications to see how you can simply do >> that. >> - the dealloc method is no more overriden. When using this version, >> you will see a bunch of errors related to that. A search and replace >> should do the trick. >> - I saw some crashes on PowerPC G4 machines with Mono 2.6. Please use >> Mono 2.4 as it is known to work ok. >> - I think there are still some hidden issues (performance, optimization, >> etc). >> >> Can you please provide feedback on: >> - the platform you are testing on (OS and Processor) >> - the Mono version you are testing with >> - the kind of application you are testing >> - the result (work or crash) >> >> Thank you to everybody who has helped, and happy testing. >> >> Regards, Laurent Etiemble. >> >> [1] https://bugzilla.novell.com/show_bug.cgi?id=537764 >> [2] http://www.mail-archive.com/[email protected]/msg00251.html >> [3] http://www.mail-archive.com/[email protected]/msg00286.html >> >> >> >
