Date: Wed, 24 Feb 2010 16:39:31 -0600 From: Peter Steele <psteele@maxiscale.com> To: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: RE: ntpd hangs under FBSD 8 Message-ID: <7B9397B189EB6E46A5EE7B4C8A4BB7CB39E95567@MBX03.exg5.exghost.com> In-Reply-To: <Pine.GSO.4.64.1002241415590.5432@zeno.ucsd.edu> References: <7B9397B189EB6E46A5EE7B4C8A4BB7CB385D5C73@MBX03.exg5.exghost.com> <20100220113349.GA22800@kiwi.sharlinx.com> <7B9397B189EB6E46A5EE7B4C8A4BB7CB385D60B7@MBX03.exg5.exghost.com> <Pine.GSO.4.64.1002241415590.5432@zeno.ucsd.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
>I bet ntpd doesn't call select() in all that many places. Instead of goin= g to all this trouble to build a debugging libc, you could just >grep for select() and place breakpoints on all occurrences. (It might als= o be obvious from looking at them which one is the offender.) I just checked--there are five calls to select. I might flag each one with = a printf or something and recompile to see which one is the culprit. >Also, since a system call is causing the trouble, you might learn somethin= g from truss or ktrace. I'll check these out...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7B9397B189EB6E46A5EE7B4C8A4BB7CB39E95567>