home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!sun-barr!cs.utexas.edu!usc!rpi!zaphod.mps.ohio-state.edu!malgudi.oar.net!ucbeh.san.uc.edu!uceng.uc.edu!babbage.ece.uc.edu!snert.ece.uc.edu!tmcbraye
- Newsgroups: comp.sys.sgi
- Subject: Re: what is /usr/lib/libmalloc_d.a?
- Message-ID: <1992Aug18.170903.24902@babbage.ece.uc.edu>
- From: tmcbraye@snert.ece.uc.edu (Tim McBrayer)
- Date: Tue, 18 Aug 1992 17:09:03 GMT
- Sender: root@babbage.ece.uc.edu (Operator)
- References: <2978@ariel.its.unimelb.EDU.AU>
- Organization: Unversity of Cincinnati, ECE Dept
- Nntp-Posting-Host: snert.ece.uc.edu
- Lines: 16
-
- In article <2978@ariel.its.unimelb.EDU.AU> paul@sunrise.sli.unimelb.edu.au (Paul Joyce) writes:
- >Subject says it all. Is it a debugging version of malloc?
- >/usr/lib/libmalloc.a is under malloc(3X), and I can guess what
- >/usr/lib/libmalloc_G0.a is (I think). But _d?
-
- Yes, this is a debugging version. If you examine the malloc(3X) man page
- (or possibly malloc.h, I forget which), you'll find references to being able
- to write out a binary debug file, containing every malloc/free, including
- all relevant data. This debug file can then be post-processed to examine
- memory allkocation behavior.
-
- Libmalloc_G0.a was compiled with the -G 0 option, I assume.
- --
- Tim McBrayer tmcbraye@thor.ece.uc.edu
- Computer Architecture Design Laboratory (513) 556-0904
- University of Cincinnati "Visualize Whirled Peas"
-