FR3 segmentation fault....

[Alan DeKok]

Did that locking code go public?  Arg... It was supposed to be for internal testing of a feature in develeopment.

Sent from my iPhone

On 2012-12-06, at 5:18 AM, Phil Mayers <p.mayers at imperial.ac.uk> wrote:

> On 12/05/2012 11:55 PM, Arran Cudbard-Bell wrote:
> 
>> Keep seeing random blocks of:
> 
> Hmm. I notice Alan added locking to the core rbtree code. Did anyone *remove* the duplicate locking in mem.c following that?
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html