Which libraries for MallocDebug

Thread View: comp.sys.mac.programmer.codewarrior

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by Raymond Wed, 26 Feb 2003 21:22

#849

Author: Raymond
Date: Wed, 26 Feb 2003 21:22

38 lines
2574 bytes

Hello

I'm writing a Mach O application with CW 8.2 on OS 10.1.5
I'd like to use MallocDebug on this application, but I cannot figure out
which libraries to include.

For the debug version of my C application, I link against:
--------------------------------------------------
crt1.o
MSL_All_Mach-O_D.lib

When I added:
------------
libMallocDebug.a

I get 6 link errors like:
-----------------------
Link Error  : undefined: 'WriteCharsToConsole' (code)
Referenced from '__write_console' in MSL_All_Mach-O_D.lib

I searched the internet and found that MWRon suggested to someone else to
include SIOUX.
So then I added:
-----------------
MSL_SIOUX_Mach-O_D.lib

And now I am down to 1 Link error:
--------------------------------------
Link Error  : undefined: '__eprintf' (code)
Referenced from 'check_mach_return' in libMallocDebug.a


Does anyone know the correct libraries to include (and the order if
relevant) to use MallocDebug in a MachO application?
Does anyone know which library to include for the eprintf symbol?

Thank you for any suggestions
ray

Re: Which libraries for MallocDebug

#850

Author: MW Ron
Date: Thu, 27 Feb 2003 17:13

65 lines
2979 bytes

In article <Qea7a.25$J51.4116730@newssvr15.news.prodigy.com>,
 "Raymond" <ray@powerproduction.com> wrote:

>Hello
>
>I'm writing a Mach O application with CW 8.2 on OS 10.1.5
>I'd like to use MallocDebug on this application, but I cannot figure out
>which libraries to include.

Basically I'd suggest you use BSD  C Headers and C Library.

put the MSL folder next to last in your access order, (just ahead of 
frameworks)   so that /usr  and  Mac OS X Support is ahead of MSL   

You will then link with the BSD C library and that version of Malloc and 
stdio.h has the information for MallocDebug

You don't need SIOUX  library in your project  instead put 
console_OS_X.c in there

You will need to run it from terminal, it won't run from the IDE.

Ron

>
>For the debug version of my C application, I link against:
>--------------------------------------------------
>crt1.o
>MSL_All_Mach-O_D.lib
>
>When I added:
>------------
>libMallocDebug.a
>
>I get 6 link errors like:
>-----------------------
>Link Error  : undefined: 'WriteCharsToConsole' (code)
>Referenced from '__write_console' in MSL_All_Mach-O_D.lib
>
>I searched the internet and found that MWRon suggested to someone else to
>include SIOUX.
>So then I added:
>-----------------
>MSL_SIOUX_Mach-O_D.lib
>
>And now I am down to 1 Link error:
>--------------------------------------
>Link Error  : undefined: '__eprintf' (code)
>Referenced from 'check_mach_return' in libMallocDebug.a
>
>
>Does anyone know the correct libraries to include (and the order if
>relevant) to use MallocDebug in a MachO application?
>Does anyone know which library to include for the eprintf symbol?
>
>Thank you for any suggestions
>ray
>
>

-- 
       Migrate your PowerPlant Applications to Windows
    http://www.metrowerks.com/MW/Services/OEM/default.htm

Ron Liechty - MWRon@metrowerks.com - http://www.metrowerks.com

Re: Which libraries for MallocDebug

#852

Author: Sean McBride
Date: Sat, 01 Mar 2003 20:25

9 lines
1319 bytes

In article <Qea7a.25$J51.4116730@newssvr15.news.prodigy.com>,
 "Raymond" <ray@powerproduction.com> wrote:

> I'm writing a Mach O application with CW 8.2 on OS 10.1.5
> I'd like to use MallocDebug on this application, but I cannot figure out
> which libraries to include.

You know you can use MallocDebug on ANY app, without adding libs or 
anything, right?  Altough I think some functionality is unavailable.

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads