3.0.1: good old "die on exit" again
a.cudbardb at freeradius.org
Mon Feb 3 12:59:15 CET 2014
On 3 Feb 2014, at 11:16, Arran Cudbard-Bell <a.cudbardb at freeradius.org> wrote:
> On 3 Feb 2014, at 10:46, Stefan Winter <stefan.winter at restena.lu> wrote:
>>> Well not very much seeing as you've not provided the backtrace.
>>> Could you try with 3.0.x and see if the issue is still present.
>>> You can use panic_action to produce the backtrace.
>> Program received signal SIGABRT, Aborted.
>> 0x00007ffff5ca4849 in raise () from /lib64/libc.so.6
>> (gdb) bt
>> #0 0x00007ffff5ca4849 in raise () from /lib64/libc.so.6
>> #1 0x00007ffff5ca5cd8 in abort () from /lib64/libc.so.6
>> #2 0x00007ffff70fdfac in ?? () from /usr/lib64/libtalloc.so.2
>> #3 0x00007ffff70fdd5e in _talloc_free () from /usr/lib64/libtalloc.so.2
>> #4 0x000000000043a6f6 in home_server_free (data=0x89eb70) at
>> #5 0x00007ffff799a522 in FreeWalker (tree=0x89dba0, X=0x89ed60) at
>> #6 0x00007ffff799a4d5 in FreeWalker (tree=0x89dba0, X=0x89e740) at
>> #7 0x00007ffff799a58e in rbtree_free (tree=0x89dba0) at <command-line>:88
>> #8 0x000000000043ac1a in realms_free () at <command-line>:251
>> #9 0x000000000041fdb4 in free_mainconfig () at <command-line>:979
>> #10 0x0000000000428e73 in main (argc=2, argv=0x7fffffffe418) at
>> (gdb) quit
Ok. Probably fixed... Home server was being alloced with normal malloc at
realms.c:1181, it wasn't in master.
It was a bug anyway, even if it wasn't the thing you're seeing, the alloced
home server was being inserted into the home_servers_byaddr tree, which uses
talloc_free as it's free callback.
Thanks for the bug report.
Arran Cudbard-Bell <a.cudbardb at freeradius.org>
FreeRADIUS Development Team
FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 881 bytes
Desc: Message signed with OpenPGP using GPGMail
More information about the Freeradius-Devel