Please check v3.0.x head

[Arran Cudbard-Bell]

> On 21 Sep 2015, at 11:04, Matthew Newton <mcn4 at leicester.ac.uk> wrote:
> 
> On Mon, Sep 21, 2015 at 08:00:06AM +0200, Stefan Winter wrote:
>> _EXIT(1) CALLED src/lib/debug.c[753].  Last error was:
>> Mon Sep 21 07:54:03 2015 : Error: Cannot update core dump limit: Operation not permitted
>> Mon Sep 21 07:54:03 2015 : Info: Core dumps are enabled
>> Mon Sep 21 07:54:03 2015 : Info: Debugger not attached
>> 
>> Since I'm running FR non-root, apparently the core dumps didn't quite
>> work, so I don't have a better backtrace, sorry.
> 
> Won't be much help without a core dump :(

All we can tell is that:

- You're running a developer build.
- RERROR or REDEBUG was called in eap_method_select.
- When adding a Module-Failure-Message attribute, talloc encountered a already freed or mangled
VALUE_PAIR or buffer.

> The error looks like you haven't set "ulimit -c 0" before starting
> FreeRADIUS?
> 
> Otherwise if it is a permissions thing and on Linux you could set a
> core pattern so it writes to, e.g. /tmp:
> 
> # echo "/tmp/core.%e.%p" > /proc/sys/kernel/core_pattern

Yep.

-Arran

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...
Name: signature.asc
Type: application/pgp-signature
Size: 872 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20150921/0be54ab0/attachment.sig>