Alan DeKok wrote:
> matthew zeier wrote:
>> What sort of additional information would be useful?
>   doc/bugs
>   i.e. WHERE the double free is.  The message you showed says "something
> went wrong.".  That's nice.  Which line of code needs to be changed?

How would I know where the double free is?  Just running 'radiusd -X' spit out 
that error just before failing to run.

>   Changing a line at random won't help.  Hence the need to know where
> the problem is.
>>  If it matters, I was 
>> having the same problem with 1.1.5.
>   Yes.  That's fixed, and will be released in 1.1.6.

How can I get that version?
List info/subscribe/unsubscribe? See

Reply via email to