Backtrace of ldap related crash
Franks Andy (IT Technical Architecture Manager)
Andy.Franks at sath.nhs.uk
Tue Sep 22 15:59:17 CEST 2015
Drat, I fixed AD (memory leak) and now it's not likely to happen again until the next time, which could be a while away.
I guess I'd best come back then :-)
Sorry about that.
From: Freeradius-Users [mailto:freeradius-users-bounces+andy.franks=sath.nhs.uk at lists.freeradius.org] On Behalf Of Alan DeKok
Sent: 22 September 2015 13:11
To: FreeRadius users mailing list
Subject: Re: Backtrace of ldap related crash
On Sep 22, 2015, at 6:16 AM, Franks Andy (IT Technical Architecture Manager) <Andy.Franks at sath.nhs.uk> wrote:
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007ffff2fc2b8a in mod_authorize (instance=0xb3c680, request=0xd5f060) at src/modules/rlm_ldap/rlm_ldap.c:1455
> 1455 if (rlm_ldap_map_do(inst, request, conn->handle, &expanded, entry) > 0) rcode = RLM_MODULE_UPDATED;
That's a weird place to have a crash. Can you do:
(gdb) p *conn
(gdb) p request
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
More information about the Freeradius-Users