From owner-freebsd-bugs Fri Oct 27 23:10:17 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 9BB9737B65E for ; Fri, 27 Oct 2000 23:10:02 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id XAA12657; Fri, 27 Oct 2000 23:10:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Fri, 27 Oct 2000 23:10:02 -0700 (PDT) Message-Id: <200010280610.XAA12657@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Bruce Evans Subject: Re: kern/2768: ktrace(1) -i dumps corrupted trace data Reply-To: Bruce Evans Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/2768; it has been noted by GNATS. From: Bruce Evans To: johan@FreeBSD.ORG Cc: j@ida.interface-business.de, freebsd-gnats-submit@FreeBSD.ORG Subject: Re: kern/2768: ktrace(1) -i dumps corrupted trace data Date: Sat, 28 Oct 2000 16:39:53 +1100 (EST) > Is this still a problem in more recent releases of FreeBSD > (for example 4.1-RELEASE)? I don't know what caused it in PR 2768, but I have seen it in -current when the ktrace output is written to an nfs filesystem. It seemed to be caused by rev.1.37 of kern_ktrace.c. ktrwrite() needs to write the header and the record atomically, but doesn't. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message