Date: Wed, 2 Aug 2006 15:35:56 -0700 (PDT) From: Kip Macy <kmacy@fsmware.com> To: Daniel Eischen <deischen@freebsd.org> Cc: freebsd-current@freebsd.org, John Birrell <jb@what-creek.com>, Tobias Gro?er <bsdlists@gmx.de> Subject: Re: DTRACE build failure (/usr/obj/usr/src/tmp/usr/bin/ld: cannot find -lpthread) Message-ID: <20060802151129.R79030@demos.bsdclusters.com> In-Reply-To: <Pine.GSO.4.64.0608021800440.8714@sea.ntplx.net> References: <1154527524.93666.22.camel@tobias.home.web-wahnsinn.de> <20060802194817.GA53062@what-creek.com> <Pine.GSO.4.64.0608021611310.8714@sea.ntplx.net> <20060802135246.J66851@demos.bsdclusters.com> <Pine.GSO.4.64.0608021706040.8714@sea.ntplx.net> <20060802141115.D71770@demos.bsdclusters.com> <Pine.GSO.4.64.0608021800440.8714@sea.ntplx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> That sounds more like a bug with gdb/libthread_db. It also doesn't
> sound like a major bug either, like "signals are broken with KSE"
> makes it sound.
Uhhhmmm no it doesn't. And even if it did, it wouldn't explain why
threaded processes become unkillable. In any event removing KSE makes
the problem go away.
I guess I'll just continue advocating for the removal of KSE after
libthr has proven itself. I've been pretty happy with nokse+libthr on
my desktop running the dtrace branch, so I think we're getting there.
-Kip
>
> > It is trivial to hit on sun4v. However, I've seen it (or a problem with
> > similar symptoms) on x86 using NetApp's development simulator which
> > makes very heavy use of signals. I believe NetApp ended up giving up on
> > using FreeBSD for running their simulator as this problem made FreeBSD a
> > non-starter for them. I no longer work for NetApp so I don't have access
> > to the sources for the simulator any more, so I don't know if bike_sched
> > fixes that problem for them or not.
> >
> > -Kip
> >
> >
> > On Wed, 2 Aug 2006, Daniel Eischen wrote:
> >
> >> On Wed, 2 Aug 2006, Kip Macy wrote:
> >>
> >>> sun4u is a dead architecture. Signals are broken with KSE on a
> >>> tightly coupled SMP so sun4v doesn't even have KSE in the tree.
> >>
> >> On every platform or on sparc64? I am unaware of any signal
> >> problems in i386.
> >>
> >>> Unless someone steps up to fix KSE "will not work" is more correct.
> >>
> >> Please clarify.
> >>
> >> --
> >> DE
> >> _______________________________________________
>
> --
> DE
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060802151129.R79030>