tech-userlevel archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: radiusd: Error detected by libpthread: Invalid mutex.

In article <>,
Edgar Fuß  <> wrote:
>Hm, I finally managed to catch FreeRADIUS in the act (by setting both
>stopfork and stopexit of teh shell and then exec'ing it, after which I
>was finally able to attach to the child.
>I set a breakpoint to pthread__errorfunc, and accoring to the backtrace,
>the problem is indeed fork(). To be precise, it's somewhere INSIDE fork():
>0x00007f7ff568d35a in __fork () from /usr/lib/
>(gdb) break pthread__errorfunc
>Breakpoint 1 at 0x7f7ff5a0b2d6
>(gdb) cont
>Breakpoint 1, 0x00007f7ff5a0b2d6 in pthread__errorfunc () from
>(gdb) bt
>#0  0x00007f7ff5a0b2d6 in pthread__errorfunc () from /usr/lib/
>#1  0x00007f7ff5a089ae in ?? () from /usr/lib/
>#2  0x00007f7fece2df14 in ldap_ld_free () from /usr/lib/
>#3  0x00007f7ff4e05ca2 in ?? () from /usr/lib/
>#4  0x00007f7ff4e076e4 in ?? () from /usr/lib/
>#5  0x00007f7ff568026e in fork () from /usr/lib/
>#6  0x000000000041b6a9 in main ()

Could be a double free. Why don't you rebuild your system with MKDEBUG=yes
and then we can better see what's going on?


Home | Main Index | Thread Index | Old Index