"Stephen J. Turnbull" <stephen(a)xemacs.org>, on Mon, 19 Aug 2002 at
00:42:27 +0900 you wrote:
How do I go about finding out what _malloc_ thinks it has allocated
here? And why would malloc make this kind of mistake?
Install the glibc sources and tell GDB "dir /path/to/glibc" before you
start. I've got the glibc sources around for other reasons, so I'll
give it a whirl.
<*Time passes*>
The problem does not occur with a no-MULE XEmacs, although it does
complain that (void-function bold). With a MULE XEmacs, I get the
error and wind up in the calloc code in GDB.
I am using a RedHat 7.2 box with glibc-2.2.4. Upgrading to the latest
update (glibc-2.2.4-29) makes the problem go away for me. Now I get the
(void-function bold), just like with the no-MULE XEmacs. And the
ChangeLog shows that releases 2.2.4-28 and 2.2.4-29 were both made to
fix bugs in calloc.
--
Jerry James, who does not believe in coincidences
http://www.ittc.ku.edu/~james/