Re: pointer parameter passed to free or realloc

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