Jakob Hirsch wrote: > I tried it, mainly to get rid of the random segfaults we get every few > days (bug #35). Unfortunately, last night it a crashed on one machine > (after running for about 60h): > >> Sep 16 04:07:22 radius64-01b kernel: [24863577.558534] ui-freeradius[20331] >> general protection ip:7f6627405b0e sp:7fff11594180 error:0 in >> libfreeradius-radius-2.1.10.so[7f66273ee000+1f000] > > backtrace: > >> #0 fr_packet_cmp (a=0x7f6618064700, b=0xf6f5bc5f78c00c80) at packet.c:139
Well... that looks like the same problem. <sigh> > Is there anything we can do to help sorting this out? Run it under 'valgrind --tool=memcheck --leak-check=full radiusd -f" It will be slow, but it may help track down the problem. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html