Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
In-Reply-To: <6.0.1.1.0.20040216163844.039274e0@127.0.0.1>
To: Cygwin List <cygwin AT cygwin DOT com>
MIME-Version: 1.0
Subject: Re: limiting strace?
From: Thomas L Roche <tlroche AT us DOT ibm DOT com>
Message-ID: <OF1CA9D509.C0CDBC38-ON85256E3C.00781279-85256E3C.007A2CB8@us.ibm.com>
Date: Mon, 16 Feb 2004 17:14:27 -0500
Content-Type: text/plain; charset="US-ASCII"

At 04:32 PM 2/16/2004, Thomas L Roche wrote:
>> I know how to use those tools to *report from* strace.out ... but
>> that's not what I'm trying to do. I don't want to say, "give me the
>> last million lines from strace.out"--windows being what it is, if
>> the file's big enough I may not get a chance to ask!

>> I want instead to say something like, "don't let strace.out get
>> bigger than a million lines," or 1GB, or something like that.

because, again, I'm concerned the *the output from strace* will be
larger than my diskspace.

Larry Hall 02/16/2004 04:42:48 PM:
> In your case, it sounds to me like you could just pipe the output of
> strace into grep looking for a keyword or two specific to the error
> message and the strace message that Chris embellished for you.

Hmm ... filter line-by-line? The problem with that (AFAICS--feel free
to inform otherwise) is loss of context: but if all Faylor wants is on
one line, I'll give

strace | fgrep 'commit memory for cygwin heap' > strace.filtered.out

a shot. (Feel free to recommend something better!)


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/