build failure

[David Relson]

At 10:12 PM 1/17/03, Clint Adams wrote:

> > Given a new compiler, it might be worth trying a build without any
> > optimizations to see what happens.
>
>Even with -O0, all tests fail.  Seems that it's related to
>MALLOC_CHECK_ :
>
>
># MALLOC_CHECK_=0
># : | ../bogofilter -peC
>X-Bogosity: No, tests=bogofilter, spamicity=nan, 
>version=0.9.2.cvs+locking.20030116
>
># MALLOC_CHECK_=1
># : | ../bogofilter -peC
>malloc: using debugging hooks
>free(): invalid pointer 0x4b030!
>free(): invalid pointer 0x4b8e0!
>free(): invalid pointer 0x4b950!
>free(): invalid pointer 0x4b920!
>free(): invalid pointer 0x4dd00!
>free(): invalid pointer 0x4e4e0!
>free(): invalid pointer 0x4e550!
>free(): invalid pointer 0x4e520!
>free(): invalid pointer 0x50900!
>free(): invalid pointer 0x50b70!
>free(): invalid pointer 0x50b80!
>free(): invalid pointer 0x720b0!
>free(): invalid pointer 0x50bb0!
>free(): invalid pointer 0x50b90!
>X-Bogosity: No, tests=bogofilter, spamicity=nan, 
>version=0.9.2.cvs+locking.20030116
>
>free(): invalid pointer 0x50b40!
>free(): invalid pointer 0x50b30!
>free(): invalid pointer 0x4de50!
>free(): invalid pointer 0x4dd40!
>free(): invalid pointer 0x720c0!
>free(): invalid pointer 0x4dcd0!
>free(): invalid pointer 0x4dc40!
>free(): invalid pointer 0x4b5d0!
>free(): invalid pointer 0x4b580!
>free(): invalid pointer 0x4b5f0!
>free(): invalid pointer 0x72100!
>free(): invalid pointer 0x4dc20!
>free(): invalid pointer 0x40301010!
>free(): invalid pointer 0x4dbc0!
>free(): invalid pointer 0x4dbf0!
>free(): invalid pointer 0x4db90!
>free(): invalid pointer 0x4bb80!
>free(): invalid pointer 0x4bb60!
>free(): invalid pointer 0x4bb30!
>free(): invalid pointer 0x4bb00!
>free(): invalid pointer 0x4b8c0!
>free(): invalid pointer 0x4baf0!
>free(): invalid pointer 0x4b670!
>free(): invalid pointer 0x4b3a0!
>free(): invalid pointer 0x4b360!
>free(): invalid pointer 0x4b390!
>free(): invalid pointer 0x4b330!
>free(): invalid pointer 0x50a50!
>free(): invalid pointer 0x50940!
>free(): invalid pointer 0x722d0!
>free(): invalid pointer 0x508d0!
>free(): invalid pointer 0x50840!
>free(): invalid pointer 0x4e1d0!
>free(): invalid pointer 0x4e180!
>free(): invalid pointer 0x4e1f0!
>free(): invalid pointer 0x72310!
>free(): invalid pointer 0x50820!
>free(): invalid pointer 0x40344010!
>free(): invalid pointer 0x507c0!
>free(): invalid pointer 0x507f0!
>free(): invalid pointer 0x50790!
>free(): invalid pointer 0x4e780!
>free(): invalid pointer 0x4e760!
>free(): invalid pointer 0x4e730!
>free(): invalid pointer 0x4e700!
>free(): invalid pointer 0x4e4c0!
>free(): invalid pointer 0x4e6f0!
>free(): invalid pointer 0x4e270!
>free(): invalid pointer 0x4dfa0!
>free(): invalid pointer 0x4df60!
>free(): invalid pointer 0x4df90!
>free(): invalid pointer 0x4df30!
>free(): invalid pointer 0x4b270!
>free(): invalid pointer 0x4b280!
>free(): invalid pointer 0x4b2f0!
>free(): invalid pointer 0x4b300!
>
># MALLOC_CHECK_=2
># : | ../bogofilter -peC
>Aborted
>
>
>Is this a glibc bug?

Could be ...  Matthias is more conversant with such details than am I.  I 
suggest double checking, using other environments.  Below are my results 
for the same test (I hope):

[root at osage tst]# MALLOC_CHECK_=0
[root at osage tst]# : | ./bogofilter -peC
X-Bogosity: No, tests=bogofilter, spamicity=nan, 
version=0.9.2.cvs+locking.0117.1940

[root at osage tst]# MALLOC_CHECK_=1
[root at osage tst]# : | ./bogofilter -peC
X-Bogosity: No, tests=bogofilter, spamicity=nan, 
version=0.9.2.cvs+locking.0117.1940

[root at osage tst]# MALLOC_CHECK_=2
[root at osage tst]# : | ./bogofilter -peC
X-Bogosity: No, tests=bogofilter, spamicity=nan, 
version=0.9.2.cvs+locking.0117.1940