× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hello All,

I need to trace what's happening on the heap.  I'm using C functions to
allocate storage and I'm trying to verify that I haven't got any memory
leaks.  Any suggestions?  I'm trying to avoid writing wrappers for
malloc(), realloc(), and free() and tracking this myself.

TRCINT supports a *HEAPMGT option but that is far too low-level (and
system wide).

MI instruction MATHSAT should help but it is broken (see later note).

MI instruction MATRMD option 0x17 is helpful (but this instruction also
has problems -- see later note).

I'm sure IBM have some internal tools for this but what are customers
supposed to do to track/locate/verify memory leaks?  Normally I'm very
careful and allocate and deallocate storage in the same function or
require my caller to allocate storage.  In this case it is messier and I
don't have much control over that (long story ...) so how do I know I'm
not leaking?

Regards,
Simon Coulter.

--------------------------------------------------------------------
   FlyByNight Software         AS/400 Technical Specialists
   http://www.flybynight.com.au/

   Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
   Fax:   +61 3 9419 0175   mailto: shc@flybynight.com.au   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.