From owner-freebsd-current Sun Feb 25 12:31:27 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 5754337B503 for ; Sun, 25 Feb 2001 12:31:23 -0800 (PST) (envelope-from daemon@mips.inka.de) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 14X7pC-0007jH-01; Sun, 25 Feb 2001 21:31:22 +0100 Received: (from daemon@localhost) by kemoauc.mips.inka.de (8.11.2/8.11.1) id f1PJuFY80569 for freebsd-current@freebsd.org; Sun, 25 Feb 2001 20:56:15 +0100 (CET) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: dump(8) segfaults Date: Sun, 25 Feb 2001 19:56:15 +0000 (UTC) Message-ID: <97bo0v$2ehn$1@kemoauc.mips.inka.de> References: <97b59k$220u$1@kemoauc.mips.inka.de> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob wrote: > Yup. Looks like it got broken. File a PR- Done. > or if you can, find out who made recent changes to dump and ask > them about it. phk did, but those changes look harmless. In fact, I just backed them out and dump still segfaults. This problem is triggered by some kernel change. dump makes serious use of signals and setjmp/longjmp... -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message