On Mon, 7 Aug 2000, Bruce McCulley wrote:
> I know I could track it down, but I'm under the gun with serious
> problems and no time, and a quick check didn't locate it on my system.
> So, where can I find the source for malloc.c to review as I try to
> locate a bug that I believe is nested in the code I inherited?
>
> THANKS!
Hehehehe.... malloc.c is part of glibc. Good luck. Therein lies some of
the most cryptic and least commented code known to mankind. But if you
must, install the source RPM (assuming redhat based system) for glibc.
If it makes you feel any better, chances are extremely good that the
problem is not in malloc.c but instead in the calling function, where you
(er, your predecessor) have overwritten some memory you don't have access
to. I'm guessing you're getting it in a call to free()? Am I close?
If so, it's probably a counting error. I ran into this myself not long
ago while writing a little combinatorics program. Overwrote the end of
the array, and free blew up. I don't remember the exact situation, but it
was something like that. I under-counted the length of the buffer by 1.
If that's not it, sorry I couldn't help... :)
--
Derek Martin
System Administrator
Mission Critical Linux
[EMAIL PROTECTED]
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
