Segfault at src/lib/misc.c:1193 in 3.0.4 (3.0.11 looks very similar)

Mike Ely me at
Fri Sep 30 23:10:16 CEST 2016

On 09/30/2016 01:59 PM, Alan DeKok wrote:
> On Sep 30, 2016, at 2:03 PM, Mike Ely <me at> wrote:
>> Unfortunately after applying the two fixes added to rlm_realm.c on 9/26 the segfault persists. Here's the latest backtrace:
>   Which is not as useful, because you've run a locally patched version.  So the line numbers don't match up with any released version, or any version in fit.
The line number corresponds to the comparison you added to the second 
update on 9/26:
275: for (i = 0; i < realm->acct_pool->num_home_servers; i++) {
276:    if (realm->acct_pool->servers[i]-> == AF_UNSPEC) continue;

>> Core was generated by `/usr/sbin/radiusd -d /etc/raddb'.
>> Program terminated with signal 11, Segmentation fault.
>> #0  0x00007f48dfea1416 in check_for_realm (instance=<optimized out>, request=0x7f48e7870830,
>>    returnrealm=0x7f48dc18d580) at src/modules/rlm_realm/rlm_realm.c:276
>> 276                             if (realm->acct_pool->servers[i]-> == AF_UNSPEC) continue;
>   The larger question is what are you doing in your configuration?

Just proxying for about half a dozen realms. Can a badly-written .conf 
file really cause radiusd to segfault?

More information about the Freeradius-Users mailing list