From owner-freebsd-current  Wed Mar 27 14:52:33 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id OAA09425
          for current-outgoing; Wed, 27 Mar 1996 14:52:33 -0800 (PST)
Received: from meter.eng.uci.edu (root@meter.eng.uci.edu [128.200.85.3])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA09418
          for <current@freebsd.org>; Wed, 27 Mar 1996 14:52:31 -0800 (PST)
Received: from newport.ece.uci.edu by meter.eng.uci.edu (8.7.4) id OAA09783; Wed, 27 Mar 1996 14:52:24 -0800 (PST)
Received: from localhost by newport.ece.uci.edu (8.7.4) id OAA29191; Wed, 27 Mar 1996 14:52:23 -0800 (PST)
Message-Id: <199603272252.OAA29191@newport.ece.uci.edu>
To: current@freebsd.org
Subject: ktrace broken in 2.2-960323-SNAP
Date: Wed, 27 Mar 1996 14:52:21 -0800
From: Steven Wallace <swallace@ece.uci.edu>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Simply add options KTRACE to the GENERIC config and make a new kernel.

Then ktrace du or your favorite program.

# kdump
...
get trace of run just fine.
...

# kdump
kdump: bogus length 0xf000ef6f

ack!  file has been corrupted somehow!
You don't have to use kdump, more or cp will work fine. The first
time the file is read, the data is correct.  The second time the
date gets thrashed.

Therefore the only way to get a ktrace is to copy the file immediatly
after the ktrace.out is generated.

This is really wierd and I haven't seen anything quite like this.

Please let me know when someone has a clue and/or has a fix.

Thanks, Steven