On Thu, Nov 30, 2006 at 11:24:05PM -0800, Alex Dubov wrote: > Greetings. > > I'm currently using apr-1.2.7 with apache 2.2.3 and recently encountered a > weird bug. I wonder if > somebody have seen something like this before (backtrace at crash point): > #0 0xb7b36462 in malloc_consolidate () from /lib/tls/libc.so.6 > #1 0xb7b37422 in _int_malloc () from /lib/tls/libc.so.6 > #2 0xb7b39231 in malloc () from /lib/tls/libc.so.6 > #3 0xb7c66b70 in pool_alloc (pool=0xfffffff0, size=977) > at memory/unix/apr_pools.c:1287 ... > It appears like there's some evil heap corruption or something like this. > Nothing interesting > shows in pool debug trace or mysql client trace. If nobody has any idea on > what can this be, I'll > have to assume that the memory is somehow corrupted by mysql and go dig there.
Yes, this is a classic symptom of heap corruption. Try running with: export MALLOC_CHECK_=2 and it may crash closer to the actual bug. Regards, joe
