Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Ross Boulet" To: Subject: RE: limiting strace?, was: failure of unzip and recent cygwin1.dll Date: Wed, 18 Feb 2004 13:28:28 -0600 Message-ID: <002301c3f655$684a2ad0$6401a8c0@RossLap> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" In-Reply-To: X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id i1IJTUCi009936 > > On Mon, 16 Feb 2004, Thomas L Roche wrote: > > > Is there a way to limit the size of the strace output _file_, rather > > than just the output file buffer, while preserving desired > > information? > > > > I previously used strace to debug the problem that 20040213 > induced in > > emacs 'desktop', therefore in emacs' startup; nevertheless the > > resulting strace.out was > 21 MB. Thus I am somewhat > hesitant to avail > > myself of > > > > Christopher Faylor Sun, 15 Feb 2004 21:12:02 -0500 > > > more strace output for the failing condition, meaning > that if you do > > > this: > > > > > strace -o strace.out unzip whatever > > > > > it should produce a large strace file. > > > > (quite the understatement :-) since > > > > * the unzip SEGVs typically occur after 30-60 min runtime > > > > * I have < 5 GB free space. > > > > Is there a way to limit the file size directly, or to script its > > rotation? > > > > Alternatively, is there a recommended mask setting that > will preserve > > the desired information, while not blowing out my disk? I'm assuming > > 'malloc' would be part of the recommended setting: anything else? > > You're on Cygwin, man! Use the scripting tools! :-) > > Don't forget that strace by default sends the trace to > stdout. You can > then pipe it to any program you wish (e.g., "tail -100", or > "grep -v ...", > or a whole bunch of others). You can then redirect the > output of the pipe > chain to a file, if you wish... > Igor > -- Just adding my 2 cents and hopefully to learn something: I know how to use pipes but I don't know how they are handled "under the covers". Wouldn't piping the strace to tail or grep still produce a temporary file of a large size? I don't know if the original poster is concerned with disk space or only the output. If it's a space issue and a temporary file is created for the pipe, I can see why he would want to limit the strace output directly. If its just the result, it seems tail or grep would be good options. Ross -- 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/