At 8:29 AM -0700 9/12/05, Ken A wrote:
Additional info:
The error " ***glibc detected *** malloc() : memory corruption" is
coming up in a pop3 client running windows. Server is running
qpopper 4.0.8, on fedora core 3 with latest patches.
Below is some info about the error message and a hint about how to
suppress this error message.
So, it looks like putting "MALLOC_CHECK_ 0" into the qpopper init
file would suppress the error message, but there seems to be a bug
in the qpopper code?
Can you reproduce this? If so, would it be possible to do so running
Qpopper under truss(1) or ktrace(1) or whatever the equivalent is on
your platform?
If there is a bug it would be good to track it down and fix it.
Thanks,
Ken
From 'man malloc'
Recent versions of Linux libc (later than 5.4.23) and GNU libc (2.x)
include a malloc implementation which is tunable via environment
variables. When MALLOC_CHECK_ is set, a special (less efficient)
implementation is used which is designed to be tolerant against
simple errors, such as double calls of free() with the same
argument, or overruns of a single byte (off-by-one bugs). Not all
such errors can be protected against, however, and memory leaks can
result. If MALLOC_CHECK_ is set to 0, any detected heap
corruption is silently ignored; if set to 1, a diagnostic is printed
on stderr; if set to 2, abort() is called immediately. This can be
useful because otherwise a crash may happen much later, and the true
cause for the problem is then very hard to track down.
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly-selected tag: ---------------
The significant problems that we face today cannot be solved at the
same level of thinking that created them. --Albert Einstein
