Laurent, any update on this issue? Thanks, Duane
On Thu, Nov 12, 2009 at 6:27 AM, Duane Wandless <du...@wandless.net> wrote: > Initial testing of the new Monobjc DLLs on Snow Leopard did NOT work for > me. > > I moved the /Library/Frameworks/Mono.Framework/Versions/2.6_M directory out > of the way so it could not be referenced. I ran my app first and received > this error: > Monobjc.ObjectiveCException: The 'libmonobjc.2.dylib' library was not > found. > > I then placed the dylib in the correct location. This verified to me that > I was using the correct version of the Monobjc DLLs. Then running my app I > still received a thread_get_state failure after a few minutes of running. > > crash report > http://pastebin.com/m65fa182f > > Switching back to using the 2.6_M mono install the thread issue did not > occur. > > Thanks for your continued efforts. > Duane > > > > > On Wed, Nov 11, 2009 at 1:33 PM, Laurent Etiemble < > laurent.etiem...@monobjc.net> wrote: > >> 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/us...@lists.monobjc.net/msg00251.html >> [3] http://www.mail-archive.com/us...@lists.monobjc.net/msg00286.html >> > >
