Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 30 Jul 2001 23:29:51 +1000 (EST)
From:      Bruce Evans <bde@zeta.org.au>
To:        Darren Reed <darrenr@reed.wattle.id.au>
Cc:        current@FreeBSD.ORG
Subject:   Re: (ref5) kdump: Cannout allocate memory
Message-ID:  <Pine.BSF.4.21.0107302315330.916-100000@besplex.bde.org>
In-Reply-To: <200107300001.KAA24098@avalon.reed.wattle.id.au>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 30 Jul 2001, Darren Reed wrote:

> Using ktrace ref5, I created ~darrenr/ktrace.out with "ktrace -i cc ..."
> but trying to print it I get:
> % kdump -f ~/ktrace.out > lout
> kdump: Cannot allocate memory
> 
> Is this stack corruption by kdump?  ref5:~darrenr/ktrace.out is available
> for anyone who wants to diagnose this further.

This is probably a corrupt ktrace record.  Atomic writing of ktrace
records seems to have been broken in rev.1.37 of kern_ktrace.c.  I've
only seen this problem when the output file is written to an nfs
filesystem.

Bruce


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0107302315330.916-100000>