Freeradius 3.0.10 sigsegv

Alan DeKok aland at deployingradius.com
Tue Jan 5 15:12:30 CET 2016


On Jan 5, 2016, at 9:08 AM, Luca Palazzo <luca.palazzo at unict.it> wrote:
> 
> Hi Alan,
> I've got these info from gdb:
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007ffff7bc77a0 in paircompare (request=request at entry=0xb10ca0, req_list=0xb10f50, check=check at entry=0xb129b0, rep_list=rep_list at entry=0x0)
>    at src/main/pair.c:536
> 536                                     if ((auth_item->da == from) || (!from)) {
> (gdb) p auth_item
> $1 = (VALUE_PAIR *) 0x2e696d696c6f7040
> (gdb) p auth_item->da
> Cannot access memory at address 0x2e696d696c6f7040

  Hmm... auth_item is corrupt.  That should only happen if there is massive memory corruption.  And that code hasn't changed for a long time.  So other people *should* have run into it.

  If you can reproduce it with a slightly modified default configuration, that would help.  I could then reproduce it locally and debug it.  Otherwise, it's hard for me to remotely debug a problem which only occurs on your machine.

  Alan DeKok.





More information about the Freeradius-Users mailing list