Article View: comp.os.msdos.programmer
Article #1351C memory debugging libraries
From: Mark Bergman
Date: Tue, 08 Sep 1992 05:25
Date: Tue, 08 Sep 1992 05:25
23 lines
1334 bytes
1334 bytes
I've got a fairly large application (~20 modules, ~15,000 lines of C)
that I'm cleaning up to compile under Turbo C. I've run into serious
memory errors at a variety of places--arrays writing over code,
pointers to the Twilight Zone, malloc calls that bomb, etc. Single
stepping execution via Turbo C's Integrated Environment hasn't helped,
besides, I hate it!
I'm looking for a memory debugging library for C. There are several
sold through the Programmer's Connection (MAD etc.). Typically they
offer error checking and verbose diagnostic reporting versions of
*alloc, free, etc. I'm interested in any experience anyone has had with
this type of debugger, and any recommendations, including ftp'able
software.
PLEASE REPLY VIA E-MAIL. I WILL ACKNOWLEDGE ALL REPLIES AND SUMMARIZE TO THE NET
----
Mark Bergman
718-855-9148
bergman@panix.com
{cmcl2,psi,uunet,apple}!panix!bergman
Technical Details
Message-ID:
<1992Sep8.052528.2493@panix.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!gatech!news.ans.net!cmcl2!panix!bergmanShow Full Headers
Complete Article Headers
Newsgroups: comp.os.msdos.programmer,comp.lang.c,alt.msdos.programmer Path: arc1-ca.pugleaf.net!sparky!uunet!gatech!news.ans.net!cmcl2!panix!bergman From: bergman@panix.com (Mark Bergman) Subject: C memory debugging libraries Summary: Advice wanted Message-ID: <1992Sep8.052528.2493@panix.com> Date: Tue, 8 Sep 1992 05:25:28 GMT Organization: PANIX Public Access Unix & Internet, NYC Keywords: DOS, Debug, Memory, Library Lines: 23