Re: pointer parameter passed to free or realloc -- MIDRANGE-L

This can also be an IBM problem - one should use F9 when viewing the message to see what procedures are involved. There are various PTFs for this message appearing in HTTPSVR and other TCP stuff. Looks like IBM is getting bit by the same thing.

It involves C code only. If you are getting this message in your code (no vendor stuff) it is probably an IBM API that is doing it.

I also went to Improved Search and found PTFs for V5R1 amd V5R2 that will leave the MCHxxxx message that triggered this thing in the job log. For V5R2 the PTF is SI07056, for V5R1 it is SI06751.

And an article from the Knowledge Base: <http://www-1.ibm.com/support/docview.wss?uid=nas146eeab82e157d4b586256b87004ab930&rs=110> that supports Scott's post - and with the PTFs installed, it may be possible to tell what actually tried to free memory - again, using F9.

HTH

Vern

At 06:28 PM 8/1/2003 -0500, you wrote:

This message is *not* benign.   There's a bug in their program that's
causing them to try to free a pointer that they didn't allocate -- which
is very scary.
Best case scenario, they're trying to free the memory twice -- which could
(although it's very unlikely) cause the program to deallocate memory
that's reserved by another program.  That other program would almost
certainly crash inexplicably, and it'd be very hard to figure out why.
Or, worst case scenario, the bug is creating a "memory leak" which could
potentially consume all of the system resources, making the system run
slow or even crash.
In any case, the problem should be fixed in the code, not ignored.
It's a serious error that should be taken seriously.
On Fri, 1 Aug 2003, Jerome Draper wrote: > > We get this error many thousands of time in our Lawson apps. Lawson says to > ignore it because it is benign and that it came as a "feature" in V5R1. > > Our log files (defined at max size) are wrapping all day long (27,000 pages). > There must be a way to suppress this message globally. > > Anyone know? > > Jerry Draper > Trilobyte Software Systems > > Message ID . . . . . . : C2M1212 Severity . . . . . . . : 30 > Message type . . . . . : Diagnostic > Date sent . . . . . . : 08/01/03 Time sent . . . . . . : 13:49:24 > > Message . . . . : The pointer parameter passed to free or realloc is not > valid. > Cause . . . . . : The pointer parameter passed to free or realloc was not > valid. This caused your function call to fail. > Recovery . . . : Correct the invalid pointer parameter being passed to free > or realloc. > Technical description . . . . . . . . : The value of the pointer passed to > free or realloc is X'800000000000000030A19DB8CD019930'. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.