Core dump on start of FR3.0.1

Alan DeKok aland at deployingradius.com
Fri Jan 17 17:16:36 CET 2014


Palmer J.D.F. wrote:
> Program received signal SIGSEGV, Segmentation fault.
> 0x00c104f6 in _talloc_free () from /usr/lib/libtalloc.so.2
> Missing separate debuginfos, use: debuginfo-install glibc-2.13-2.i686 keyutils-libs-1.2-6.fc12.i686 krb5-libs-1.8.4-2.fc14.i686 libcom_err-1.41.12-6.fc14.i686 libselinux-2.0.96-6.fc14.1.i686 libtalloc-2.0.1-1.fc13.i686 ncurses-libs-5.7-9.20100703.fc14.i686 nss-softokn-freebl-3.12.10-1.fc14.i686 openssl-1.0.0e-1.fc14.i686 readline-6.1-2.fc14.i386 zlib-1.2.5-2.fc14.i686
> (gdb) bt
> #0  0x00c104f6 in _talloc_free () from /usr/lib/libtalloc.so.2
> #1  0x00118e99 in cf_item_parse (cs=0x80acd78, name=0x8086183 "prefix", type=100, data=0x8096044,
>     dflt=0x808618a "/usr/local") at src/main/conffile.c:954

  Hmm... that shouldn't happen.  If you still have the gdb process
around, can you do:

(gdb) up
(gdb) p *q

  That should tell a *bit* more information.  Also, please double-check
that you don't have any 3.0.0 libraries around.  That's another
potential source for confusion.

  Alan DeKok.


More information about the Freeradius-Users mailing list