From owner-freebsd-hackers Fri Apr 13 10:31:20 2001 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 006C737B507 for ; Fri, 13 Apr 2001 10:31:16 -0700 (PDT) (envelope-from crossd@spigot.cs.rpi.edu) Received: from spigot.cs.rpi.edu (spigot.cs.rpi.edu [128.113.96.204]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id NAA07979 for ; Fri, 13 Apr 2001 13:31:14 -0400 (EDT) Message-Id: <200104131731.NAA07979@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: ypserv (on -RC/-STABLE)... almost there Date: Fri, 13 Apr 2001 13:31:14 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have trace the problem in ypserv down to the RPC dispatch routines.. I am digging further and I hope to have it found and eliminated today (in time for -RELEASE ;) If anyone has any idea how it could be tripping up here, please let me know. My 2 guesses are a corrupted svc_callback entry (no idea how it is getting corrupted, yet.) or there is something walking on stuff within ypprog_1 or ypprog_2 (I don't know yet if the segfault is the (sc->dispatch) call in svc.c in the rpc library, or if it is within the function that sc->dispatch calls (the next seg-fault will let me know this.) -- 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