× 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.


  • Subject: Re: Finding Memory Leaks in ILE C
  • From: "David Morris" <dmorris@xxxxxxxxxxxxx>
  • Date: Wed, 01 Mar 2000 17:41:20 -0700

Dan,

One technique is to create a wrapper around your memory functions and call a 
logging 
function when in debug or ?.  Last October or November, Midrange Computing 
published 
a set of procedures (in RPGIV) that performs memory allocation as well as 
logging if a 
global variable is set.  The procedures support heap, user space, and *LDA 
storage.  I 
think the article was titled "Stick it in Storage", if you are interested, I 
can find the source 
and mail you the link.

David Morris

>>> Dan.Tyer@smed.com 03/01/00 04:25PM >>>


Let me apologize for posting a non-RPG question on this list, but my
desperation exceeds my etiquette.  We are mostly an RPG shop but are
developing some new applications in C on the AS/400 (no commentary,
please!) and are having our share of problems tracking down memory leaks.
Does anyone know of any tools for detecting memory leaks (along the lines
of  Electric Fence, MemTrace, Memory Sleuth, or numerous others) that run
on the AS/400?  Responses are much appreciated.

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.