From owner-freebsd-current Sun Jul 29 17: 1:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from CPE-61-9-164-106.vic.bigpond.net.au (unknown [144.137.9.200]) by hub.freebsd.org (Postfix) with ESMTP id D1E9E37B401 for ; Sun, 29 Jul 2001 17:01:45 -0700 (PDT) (envelope-from darrenr@reed.wattle.id.au) Received: (from root@localhost) by CPE-61-9-164-106.vic.bigpond.net.au (8.11.0/8.11.0) id f6U01hN17303 for ; Mon, 30 Jul 2001 10:01:43 +1000 (EST) From: Darren Reed Message-Id: <200107300001.KAA24098@avalon.reed.wattle.id.au> Subject: (ref5) kdump: Cannout allocate memory To: current@freebsd.org Date: Mon, 30 Jul 2001 10:01:39 +1000 (EST) X-Mailer: ELM [version 2.4ME+ PL37 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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. FYI: % limit cputime unlimited filesize unlimited datasize 524288 kbytes stacksize 65536 kbytes coredumpsize unlimited memoryuse unlimited descriptors 2088 memorylocked unlimited maxproc 1043 I can't see that I've got any special malloc debugging things defined either in environment variables or elsewhere. Darren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message