whilst building /usr/ports/java/jdk13 on FreeBSD 4.6.2-RELEASE #0
with a ports tree cvsup'ed as of today (Nov 3, 2002) I gained a
few sed.core files...
./work/j2sdk1.3.1/make/sun/font/sed.core
and on a different system (same o/s)
./work/j2sdk1.3.1/make/javax/sound/sed.core
./work/j2sdk1.3.1/make/sun/awt/sed.core
Part of the output from the "make" is...
/native/sun/awt/../java2d/loops
-I../../../src/share/native/sun/awt/../java2d/pipe
-I../../../src/share/native/sun/awt/../dc/doe
-I../../../src/share/native/sun/awt
/../dc/path -I../../../src/solaris/native/sun/awt/../jdga
../../../src/solaris/na
tive/sun/awt/awt_GlobalCursorManager.c 2> /dev/null | \
/usr/bin/sed -e
's!awt_GlobalCursorManager\.o!../../../build/bsd-i386/tmp/sun/
sun.awt/awt/obj/&!g' >
../../../build/bsd-i386/tmp/sun/sun.awt/awt/obj/awt_GlobalC
ursorManager.d
Illegal instruction - core dumped
The "make" stopped that time. A "make clean" and another make, and it
finished to completion, but still left a few different sed.cores around.
On 2 other machines (same o/s) process worked fine and sed didn't dump
at all.
In all cases, the resulting jdk worked (tested with uportal)
It remains my goal to isolate the particular command that sed dumps on,
and replicate it, in a repeatable way.
------------------------------------------------------------------------
Bruce Campbell
Engineering Computing
University of Waterloo
http://www.eng.uwaterloo.ca/~bruce/
519-888-4567 ext. 5889
PGP Key: http://www.eng.uwaterloo.ca/~bruce/public.txt
Tune: E3E3A3A3A3A3 A3A3B3B3C3C3A3A3E3E3A3A3A3A3 \
A3A3B3B3C3C3A3A3E3E3D3D3D3D3B3B3C3C3D3D3D3+E3-E3E3 \
A4A4 A4A4A4A4 A4A4G3G3F3F3E3E3F3F3G3G3 G3G3G3G3 \
G3G3F3F3E3E3D3D3E3E3F3F3 F3F3 B3B3C3C3D3D3E3E3E3\
E3
with "unsubscribe freebsd-java" in the body of the message