From owner-freebsd-hackers Tue Sep 25 12:27:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 612EC37B40C for ; Tue, 25 Sep 2001 12:27:35 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.6/8.11.2) id f8PJN3103708; Tue, 25 Sep 2001 12:23:03 -0700 (PDT) (envelope-from dillon) Date: Tue, 25 Sep 2001 12:23:03 -0700 (PDT) From: Matt Dillon Message-Id: <200109251923.f8PJN3103708@earth.backplane.com> To: Peter Wemm Cc: Ian Dowse , Julian Elischer , hackers@FreeBSD.ORG Subject: Re: VM Corruption - stumped, anyone have any ideas? References: <20010925032250.57FF03808@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :I had been contemplating making a fake 'struct user' in userland only in :order to keep the a.out coredump reader code happy. The a.out coredump :code (see cpu_coredump() in */*/vm_machdep.c) can generate this fake :structure in order to keep gdb happy. But then I realized that a.out :coredump debugging was almost totally irrelevant these days. : :Cheers, :-Peter :-- :Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au Hmm. How about this... if we keep the guard field at the end of struct user we could #ifdef _KERNEL it so userland doesn't notice it. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message