Subject: Re: sh core dumps
To: Valeriy E. Ushakov <firstname.lastname@example.org>
From: Rick Kelly <email@example.com>
Date: 10/20/2005 14:31:31
Valeriy E. Ushakov said:
>It seem that I can reliably reproduce the problem with devel/gmake
>after running make there I can cd to work/make-3.80 and trigger the
>bug by running ./config.status. That gives me one or sometimes two sh
>core files (i run with kern.defcorename=%n.%p.core). Both are from
>backticked invocation of sed. As we get sh.core, not sed.core that
>should happen in the vforked child before exec.
I just tried this with -current source from September 26.
cpu0 at mainbus0: MB86904 @ 110 MHz, on-chip FPU
cpu0: 16K instruction (32 b/l), 8K data (16 b/l): cache enabled
CPUFLAGS = -mv8 -mtune=supersparc
makeoptions CPUFLAGS="-mv8 -mtune=supersparc"
I ran config.status without any problems.
Rick Kelly firstname.lastname@example.org
<http://rkba.rmkhome.com/> - the right to keep and bear arms
<http://wolf.rmkhome.com/> - firearm forums