Date: Tue, 28 Jun 2005 15:47:24 +0200 From: Michael Nottebrock <lofi@freebsd.org> To: Daniel Eischen <deischen@freebsd.org> Cc: freebsd-stable@freebsd.org Subject: Re: kpdf crashes with LIBPTHREAD_SYSTEM_SCOPE set (Was: Re: FreeBSD MySQL still WAY slower than Linux) Message-ID: <200506281547.33134.lofi@freebsd.org> In-Reply-To: <Pine.GSO.4.43.0506280040570.23758-100000@sea.ntplx.net> References: <Pine.GSO.4.43.0506280040570.23758-100000@sea.ntplx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart1850362.CSu4ZpBRmK Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday, 28. June 2005 06:43, Daniel Eischen wrote: > I can't reproduce it in -current. > > -bash-2.05b$ uname -a > FreeBSD orion 6.0-CURRENT FreeBSD 6.0-CURRENT #0: Thu May 5 13:29:41 EDT > 2005 Yeah, you already said that before. So where do we go from here? Should I t= ry=20 to get a backtrace of the crash? With gdb? Ktrace? Should I compile=20 libpthread of other parts of the system with special debug flags? Should I= =20 report this on freebsd-threads instead? Or should I just let the issue go? =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart1850362.CSu4ZpBRmK Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBCwVT1Xhc68WspdLARAt4HAJ0aWK7+1ikex02/Nr1Hq6jc8twZhACgpNnm FFd8PuVLcCOs1pSOpKBGXUw= =ixEq -----END PGP SIGNATURE----- --nextPart1850362.CSu4ZpBRmK--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200506281547.33134.lofi>