From owner-freebsd-hackers Wed May 31 12:11:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 7EF2337BE9E for ; Wed, 31 May 2000 12:11:19 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (crossd@wwwpal.cs.rpi.edu [128.113.96.187]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id PAA81975; Wed, 31 May 2000 15:10:18 -0400 (EDT) Message-Id: <200005311910.PAA81975@cs.rpi.edu> To: Matthew Dillon Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: PR #10971, not dead yet. In-Reply-To: Message from Matthew Dillon of "Wed, 31 May 2000 10:23:07 PDT." <200005311723.KAA30252@apollo.backplane.com> Date: Wed, 31 May 2000 15:10:17 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If you can reproduce the problem regularly then I recommend putting > a signal guard in to see if the corruption is being caused by the > signal interrupting at an inausipcious moment. > > In main() block SIGHUP, SIGINT, SIGTERM, and SIGCHLD using sigsetmask(). > > Just prior to the select call unblock the signals. > > Just after the select call reblock the signals. > > And see if the corruption still occurs. If this fixes the problem, > then there is probably something in the reaper() (in yp_main.c) > that is causing corruption, probably by ripping a structure out from > under whatever piece of code the signal happens to interrupt. > > I took a quick look at the code and as far as I can tell it implements > no guards whatsoever. The inetd code had similar problems in the past. Alas, this is not something I have been able to reliably reproduce, it seems to trigger itself every so-often (and at inconvienient times). But no matter what I do by myself it will not trip. -- David Cross | email: crossd@cs.rpi.edu Lab Director | Rm: 308 Lally Hall Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message