Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!uunet!kddlab!cs.titech!wnoc-tyo-news!sranha!sran230!utashiro From: utashiro@sra.co.jp (Kazumasa Utashiro) Newsgroups: comp.lang.perl Subject: Re: mg, causes numerous core dumps Message-ID: Date: 25 Jun 91 06:36:43 GMT References: Sender: news@sran230.sra.co.jp Organization: Software Research Associates, Inc., Japan Lines: 43 Nntp-Posting-Host: ext12 In-reply-to: sherman@unx.sas.com's message of 22 Jun 91 11:23:36 GMT In article sherman@unx.sas.com (Chris Sherman) writes: >A few months ago, somebody posted a little gem called mg, which was a >really fancy grep command which could do all kinds of neat things. Thank you. I thought it is not so valuable because I had only a few responses. I couldn't use 4.009 or 4.010 by now because I just came back to Tokyo from USENIX and INET'91 trip. (I still don't know how tchrist look like because I didn't take Perl tutorial...) >Well, it causes perl to dump core repeatedly now. I wish I had a non-stripped >'-g' perl sitting around so I could give you a stack trace, but it shouldn't >be too hard to reproduce the effect. I had some README's sitting in a >directory, so I did a: > % mg " or " RE* > Segmentation fault (core dumped) > >If perl doesn't core dump, then the program just doesn't work, or it doesn't >work correctly. I can't find a situation where it does work anymore. I think >it is a reg exp problem since some of the fantatic looking errors look like: As Tom Christiansen sais, it is because mg uses m//g syntax for higher versions than 4.003. I built 4.009 and 4.010 today and had same result as yours. I was thinking about adding cheking mechanism without $] comparison, but it seems very difficult to avoid core dump. So I think the easiest way to make it to work is removing period in condition like this. 114c114 < if ($] > 4.003) { --- > if ($] > 4003) { I'll post updated version when m//g became available. --- K. Utashiro utashiro@sra.co.jp