radmin SIGABRTs freeradius 2.1.1

[Alan DeKok]

Norbert Wegener wrote:
> I have an input file for radmin with the following content:
> 
> debug file /var/log/radius/nw2.log
> debug condition '(NAS-IP-Address == "172.31.110.147") || (NAS-IP-Address
> == "172.31.110.149") || (NAS-IP-Address == "149.246.185.169")'

  Hmmm... that should work.

> When those commands have been executed  and some debugging shows up int
> the logfile, I want to switch to another log.
> changing the radmin input file to
> 
> debug file /var/log/radius/nw3.log
> debug condition '(NAS-IP-Address == "172.31.110.147") || (NAS-IP-Address
> == "172.31.110.149") || (NAS-IP-Address == "149.246.185.169")'
> and executing the commands, freeradius in the actual 2.1.1 version dies.

  OK.  It may be some race condition in the server core.  I'll take a look.

> Program received signal SIGABRT, Aborted.
> [Switching to Thread 47318162851936 (LWP 2820)]
> 0x00002b091e299b95 in raise () from /lib64/libc.so.6
> (gdb) bt
> #0  0x00002b091e299b95 in raise () from /lib64/libc.so.6
> #1  0x00002b091e29af90 in abort () from /lib64/libc.so.6
> #2  0x00002b091e2d035b in __libc_message () from /lib64/libc.so.6
> #3  0x00002b091e2d534e in malloc_printerr () from /lib64/libc.so.6
> #4  0x00002b091e2d695c in free () from /lib64/libc.so.6

  Yes... the memory was already free'd, most likely.  I don't think git
head ("stable" tree) has any changes in this area.

  Alan DeKok.