Date: Sun, 13 Apr 2003 22:10:23 +0200 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Christoph Kukulies <kuku@physik.rwth-aachen.de> Cc: freebsd-current@freebsd.org Subject: Re: what could have happened to mpd, ng? Message-ID: <2448.1050264623@critter.freebsd.dk> In-Reply-To: Your message of "Sun, 13 Apr 2003 20:27:59 %2B0200." <200304131827.h3DIRxa21878@accms33.physik.rwth-aachen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <200304131827.h3DIRxa21878@accms33.physik.rwth-aachen.de>, Christoph Kukulies writes: >Since I rebuilt -current (today again) my vpn >connections don't work anymore. > >Shortly after reboot I can ping the opposite side of a vpn >connection. But trying to connect via ssh already results in the >opposite side refusing me and pinging after that I get >no buffer space available. And from then on I can't even ping the opposite >side. > >And I have this bad malloc when mpd starts up. That could be the root cause. You should really try to track that down. If you can find the address from which malloc is called and use addr2line -e kernel.debug $address it should give you the line number with the bug. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2448.1050264623>