Open Menu
Close Menu
Apple
Shopping Bag
Apple
Mac
iPad
iPhone
Watch
TV
Music
Support
Search apple.com
Shopping Bag
Lists
Open Menu
Close Menu
Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists
MallocDebug is a bit to strict when launching an app
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
MallocDebug is a bit to strict when launching an app
Subject
:
MallocDebug is a bit to strict when launching an app
From: Alin Pilkington <
email@hidden
>
Date: Mon, 28 Jun 2004 14:48:07 -0700
Hi,
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:
__isctype() __istype()
This of course does not prevent the app from linking and running...only a duplicate reference warning is given. However, when I try to check for leaks using MallocDebug (and launch the app from within MallocDebug), MallocDebug terminates the launch of the app and gives the reason for the error as the warning about the duplicate references. Actually, that is not totally correct...the app "crashes" with a crash report dialog stating this is the reason for the crash but this only happens when launched from MallocDebug so this is where I suspect the problem is. This is totally unnecessary since these warnings have nothing to do with the apps ability to execute. Can you (Apple) apply some more logic to only abort the launch when it really makes sense?
Many thanks!
Alin Pilkington
P.S. I got around the problem by removing Metrowerks version of these functions and rebuilding their BSD runtime library so this is not a show stopper by any means...
_______________________________________________
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.
Follow-Ups
:
Re: MallocDebug is a bit to strict when launching an app
From:
Eric Albert <email@hidden>
Prev by Date:
MallocDebug error - getUnreferencedData [19780]
Next by Date:
WWDC / XCode v2.0?
Previous by thread:
Fwd: MallocDebug error - getUnreferencedData [19780]
Next by thread:
Re: MallocDebug is a bit to strict when launching an app
Index(es):
Date
Thread