Re: MallocDebug is a bit to strict when launching an app
Re: MallocDebug is a bit to strict when launching an app
- Subject: Re: MallocDebug is a bit to strict when launching an app
- From: Eric Albert <email@hidden>
- Date: Tue, 29 Jun 2004 00:54:37 -0700
On Jun 28, 2004, at 2:48 PM, Alin Pilkington wrote:
We are using CW 9.2 for development and are creating a BSD Mach-O
target. Metrowerks has supplied a BSD runtime library to link against
to satisfy references to items not contained in the Apple dynamic BSD
libraries. This works out good except for 2 symbols which are defined
in both libraries:
MallocDebug terminates the launch of the app and gives the reason for
the error as the warning about the duplicate references.
MallocDebug inserts a library with a special version of malloc (and
other functions, I think) into your application. To get the library
insertion to work (and override the existing versions of those
functions), it has to run your application with
DYLD_FORCE_FLAT_NAMESPACE set to 1. When running with a flat
namespace, you can't have libraries with conflicting symbols. That's
why your workaround of removing the symbols works -- you don't have any
conflicting symbols any more, so your application can run with a flat
namespace.
If this is troublesome for you, I'd suggest filing a bug report with
Apple asking for MallocDebug to work correctly with two-level
namespaces.
Hope this helps,
Eric
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.