Re: sed oddity
On Wed, 17 Jan 1996, Siggy Brentrup wrote:
> While building the gcc-2.7.2-3 package, the configure script failed
> sometimes. I tracked that down to sed dumping core when called in the
> pipe
>
> basic_machine=`echo $1 | sed 's/-[^-]*$//'`
>
> $1 is i486-unknown-linux at that point.
>
> After it had failed once, I could reproduce the error anytime I
> manually invoked the pipe inside the backquotes, so I decided to
> rebuild sed from the sources (maybe it suffered from a buggy gcc).
> The freshly built sed (invoked with ./sed) did the right thing.
> Don't know why I tried /bin/sed again, to my surprise it was working
> too!!!
Does it mean you cannot reproduce the error anymore with the old sed?
That may be a hardware error or a glitch in the kernel 1.3.50.
> On my development machine I'm running an ELF-compiled kernel 1.3.50,
> the following might be of interest too:
>
> $ ls -l /bin/sed sed-2.05/sed
> -rwxr-xr-x 1 root root 53993 Dec 1 21:10 /bin/sed
A sed produced on this day was linked before the public libc.so.5.2.1[68].
An incompatibility is remote possible. This should be reproducible.
mfg
Rolf Rossius
Reply to:
- References:
- sed oddity
- From: Siggy Brentrup <bsb@beck.westfalen.de>