From owner-freebsd-stable Thu Apr 19 17:23: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 4585037B43C; Thu, 19 Apr 2001 17:22:53 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id UAA69493; Thu, 19 Apr 2001 20:22:51 -0400 (EDT) Message-Id: <200104200022.UAA69493@cs.rpi.edu> To: wpaul@FreeBSD.ORG (Bill Paul) Cc: crossd@srs.cs.rpi.edu (David E. Cross), stable@FreeBSD.ORG, developers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: ypserv In-Reply-To: Message from wpaul@FreeBSD.ORG (Bill Paul) of "Thu, 19 Apr 2001 17:09:27 PDT." <20010420000927.E7F2737B42C@hub.freebsd.org> Date: Thu, 19 Apr 2001 20:22:51 -0400 From: "David E. Cross" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, I at least changed the subject line. I have modified the ypserv yp_dblookup dbptr entry to have 'key' be a 'char key[YPMAXRECORDSIZE];' entry and bcopy the keys in each time, it is still seg-faulting on a regular schedule. I just cannot figure out what is causing this anymore. It _must_ be in the Berkley DB code. Alas, because of stack corruption, the dump files are *useless*. -- 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-stable" in the body of the message