On Oct 23, 2009, at 8:40 AM, Nick Rogers wrote: > Thanks for the reply. > The app actually works as a launcher of another app with root privileges (its > only job is this). > Hence its a standard cocoa project with the following frameworks: > CoreFoundation, Cocoa, AppKit, CoreData, Foundation and Security frameworks.
To debug the problem, I would suggest turning on the DYLD_PRINT_LIBRARIES environment variable and see if it stops printing at a certain library, then check to make sure that library is both 64 bit and GC capable. However, for best performance on 10.5.x, I would suggest compiling your launcher app as a 32/64 bit application. 32 bit applications on 10.5.x will be more efficient in that the 32 bit chunks of all the shared frameworks are always "kept hot" by other applications -- you'll tend to page less under memory pressure with a 32 bit app on 10.5.x. (The opposite is true on Snow Leopard and, as more and more applications go 64 bit, it'll become more-so over time). b.bum _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
