net/avahi-app core dumps signal 11
robert.burmeister at utoledo.edu
Mon Jan 27 20:50:00 UTC 2014
Brad Karp wrote
> Thanks for the suggestion, but I believe this is not the cause of the
> SIGSEGV in avahi-daemon.
> I was aware of the move of libiconv into the base system, and when I
> upgraded to 10.0-RELEASE, did exactly as you suggest: I removed the
> libiconv package and forced an upgrade of all ports, so that they'd
> link against the base system's libiconv.
> I've further verified with ldd "/usr/local/lib/lib*.so*" that I have
> no shared libraries left in /usr/local/lib that were built with
> dependencies on the old /usr/local/lib/libiconv.so.3. (That is, this
> ldd command gives no "not found" errors.)
> I therefore suspect that the cause lies elsewhere. Where exactly, I
> have unfortunately not yet ascertained. Other suggestions, anyone?
> (FWIW, there is also discussion of this problem, which is being
> experienced by others, on the forums:
> http://forums.freebsd.org/viewtopic.php?f=5&t=44521 .)
> - -Brad
People who deleted all ports, removed /usr/local and reinstalled
have reported that they do not have the problem.
I have deleted the contents of /usr/local/lib and am running a portupgrade
I'll report back if that is a quicker fix.
View this message in context: http://freebsd.1045724.n5.nabble.com/net-avahi-app-core-dumps-signal-11-tp5878518p5880548.html
Sent from the freebsd-ports mailing list archive at Nabble.com.
More information about the freebsd-ports