Crash on x64?

[Phil Mayers]

Alex Balashov wrote:
> Ah, for a clearer picture, I tried running under gdb with the no-fork 
> option:
> 
> *** glibc detected *** /usr/sbin/radiusd: free(): invalid pointer: 
> 0x00002ac95891ca60 ***
> (no debugging symbols found)
> ======= Backtrace: =========
> /lib64/libc.so.6[0x2ac954229634]
> /lib64/libc.so.6(cfree+0x8c)[0x2ac95422cc5c]
> /usr/lib64/libpq.so.4[0x2ac95726cdf2]
> /usr/lib64/rlm_sql_postgresql.so[0x2ac957061e12]
> /usr/lib64/rlm_sql.so(rlm_sql_query+0x63)[0x2ac956e5db33]
> /usr/lib64/rlm_sql.so[0x2ac956e5c271]
> /usr/sbin/radiusd(modcall+0xb2)[0x2ac952c0dc52]
> /usr/sbin/radiusd[0x2ac952c0e241]
> /usr/sbin/radiusd(modcall+0x27c)[0x2ac952c0de1c]
> /usr/sbin/radiusd(rad_accounting+0xcd)[0x2ac952c056ed]
> /usr/sbin/radiusd(rad_respond+0x11a)[0x2ac952c0f1ea]
> /usr/sbin/radiusd[0x2ac952c15e51]
> /lib64/libpthread.so.0[0x2ac9534812f7]
> /lib64/libc.so.6(clone+0x6d)[0x2ac954289b6d]
> ======= Memory map: ========

> Any idea what gives there?
> 
> 

Well, it's an invalid "free", obviously, which indicates pointer 
corruption or something similar. What's odd is that we're running a 
relatively high-volume server on RHEL5 & Postgres and it's fine.

Which version of FreeRadius is this?