From owner-freebsd-questions Sun May 4 13:38:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA15956 for questions-outgoing; Sun, 4 May 1997 13:38:19 -0700 (PDT) Received: from buffnet4.buffnet.net (buffnet4.buffnet.net [205.246.19.13]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA15951 for ; Sun, 4 May 1997 13:38:15 -0700 (PDT) Received: from buffnet11.buffnet.net (shovey@buffnet11.buffnet.net [205.246.19.55]) by buffnet4.buffnet.net (8.7.5/8.7.3) with SMTP id QAA06842; Sun, 4 May 1997 16:39:17 -0400 (EDT) Date: Sun, 4 May 1997 16:38:57 -0400 (EDT) From: Steve To: Steve Howe cc: freebsd-questions@FreeBSD.ORG Subject: Re: Weird perl problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 4 May 1997, Steve Howe wrote: > On Sun, 4 May 1997, Steve wrote: > > i noticed while opening a few Megs of text files with "joe" editor, > my terminal went completely nut, shell and everything, and i have > to exit to the login prompt to regain control. i'm not an expert > on BSD RAM usage, but i something goes nuts when it gets amxed out. > i think perl sucks in that file as one long string into memory. > i wonder if it would crash if you chopped the file in 2 or 4 ... The thing is, it load the data and does the math, and is done with the file. Its when it print out what it found is when it chokes - and at 8192 bytes.