apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Dubov <oa...@yahoo.com>
Subject Weird crash in apr_palloc
Date Fri, 01 Dec 2006 07:24:05 GMT

I'm currently using apr-1.2.7 with apache 2.2.3 and recently encountered a weird bug. I wonder
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
#4  0xb7c67b97 in apr_palloc (pool=0x80d2b80, size=977)
    at memory/unix/apr_pools.c:2242
#5  0xb7edbe52 in dbd_mysql_pvselect (pool=0x80d2b80, sql=0x80b4648,
    res=0xbf92f2d4, statement=0x80a6270, random=0, args=0x80d2b80 "&#65533;\v\b")
    at dbd/apr_dbd_mysql.c:712
#6  0xb7eda944 in apr_dbd_pvselect (driver=0x48, pool=0x80d2b80,
    handle=0x80b4648, res=0xbf92f2d4, statement=0x80a6270, random=0)
    at dbd/apr_dbd.c:300

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,
have to assume that the memory is somehow corrupted by mysql and go dig there.

The crush is apparently access timing dependent. It may happen in malloc (like presented)
or later
in free when pool is destroyed or never happen at all.

I'm using my own apr_dbd_mysql (I posted it here some time before), but I can't see anything
unusual in it.

Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.

View raw message