3.0.x HEAD crashing (was hanging)
a.cudbardb at freeradius.org
Tue Jun 17 14:32:45 CEST 2014
On 17 Jun 2014, at 12:29, Phil Mayers <p.mayers at imperial.ac.uk> wrote:
> On 17/06/14 12:24, Phil Mayers wrote:
>> Current state of talloced memory:
>> CAUGHT SIGNAL: Segmentation fault
> Note the talloc dump seems to fail because of:
> #1 0x00007ffff7b999a8 in fr_log_talloc_report (ctx=0x9ebb10) at src/lib/debug.c:602
> 602 null_ctx = talloc_get_name(NULL);
> ...which ends up in:
> #0 talloc_get_name (ptr=0x0) at ../talloc.c:1153
> 1153 struct talloc_chunk *tc = talloc_chunk_from_ptr(ptr);
> ...which segfaults; not sure if talloc_get_name(NULL) is legal, or if this is a result of the bug or what?
I'm honestly not sure. To be safe i've changed the code... It wasn't wrong, but it's the sort of thing that might break between talloc versions.
Anyway, the SEGV is secondary, the issue here is bad parenting of the VALUE_PAIR. Could you use latest head and try again?
If you run it in with:
PANIC_ACTION="gdb %e %p" radiusd -lstdout -f
It'll dump you into an interactive GDB prompt, and you can poke around a bit.
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