*BSD News Article 57086


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.uwa.edu.au!classic.iinet.com.au!swing.iinet.net.au!news.uoregon.edu!news.jsums.edu!despina.neptune.com!usenet.eel.ufl.edu!news.mathworks.com!fu-berlin.de!zib-berlin.de!news.tu-chemnitz.de!irz401!uriah.heep!news
From: j@uriah.heep.sax.de (J Wunsch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Trouble With Sed on 2.1 SNAP
Date: 7 Dec 1995 21:30:46 GMT
Organization: Private BSD site, Dresden
Lines: 15
Message-ID: <4a7me6$jns@uriah.heep.sax.de>
References: <49oluq$28o@crl2.crl.com>
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
NNTP-Posting-Host: localhost.heep.sax.de
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Newsreader: knews 0.9.3

kaila@crl.com (Christine Maxwell) writes:

> There is a problem however.  Every time I attempt to compile a program 
> using sed as part of the configure, sed core dumps.

Either take the time to analyze the core dump, or use GNU sed, or
strip your sed script down to what is needed to reproduce the core
dump, and file a bug report (send-pr(1)).

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)