X-Spam-Check-By: sourceware.org Message-ID: <45DB66ED.5070700@cygwin.com> Date: Tue, 20 Feb 2007 16:23:57 -0500 From: "Larry Hall (Cygwin)" Reply-To: cygwin AT cygwin DOT com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.9) Gecko/20061221 Fedora/1.5.0.9-1.fc4.remi Thunderbird/1.5.0.9 Mnenhy/0.7.4.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: ls output still truncated References: <45DB4B01 DOT 90002 AT cygwin DOT com> <45DB56F4 DOT 60800 AT cygwin DOT com> <9ae083a20702201313k52dad10frf49a192d126bc56 AT mail DOT gmail DOT com> In-Reply-To: <9ae083a20702201313k52dad10frf49a192d126bc56@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Frodak Baksik wrote: > On 2/20/07, Chuck wrote: > >> Your wish is my command. Attached are two strace output files. The names >> should be self-explanatory. Please let me know if you see anything. In >> the mean time I'm going to refresh myself on the use of gcc and gdb and >> see if I can trace the execution of ls. Like I said in another post >> though, it's been a *very* long time since I've done any C programming >> and I don't think I've ever used the gnu debugger. > > > I'm using gmail and the traces are embedded in the email, so forgive > me if I'm way off base. > > If these are the full traces, then when it works ls runs fine. When > it doesn't work ls was killed somehow. In the first trace file the > last line is: >> 62 11096 [main] ls 1036 normalize_win32_path: c:\Program >> Files\QuickTime\QTSystem\ = normalize_win32_path (c:\Program >> Files\QuickTime\QTSystem\) > > Notice that ls never performed a closedir or wrote any data out. > > The last trace file shows: >> 167 41916 [main] ls 3048 fhandler_disk_file::closedir: 0 = >> closedir (0x6A1A60) >> 178 42094 [main] ls 3048 closedir: 0 = closedir (0xA0000) >> 113 42207 [main] ls 3048 fhandler_base::fstat: here >> 59 42266 [main] ls 3048 fstat64: 0 = fstat (1, 0x22BA20) >> 372 42638 [main] ls 3048 sig_send: sendsig 0x6FC, pid 3048, signal >> -34, its_me 1 >> 65 42703 [main] ls 3048 sig_send: wakeup 0x6C8 >> 68 42771 [main] ls 3048 sig_send: Waiting for pack.wakeup 0x6C8 >> 66 42837 [sig] ls 3048 wait_sig: signalling pack.wakeup 0x6C8 >> 72 42909 [main] ls 3048 sig_send: returning 0x0 from sending >> signal -34 >> 105 43014 [main] ls 3048 fhandler_base::write: binary write > > Which got to the point where ls closed the dir handle and actually > wrote some data. > > I don't know what would kill a process like that? Or am I just not > seeing all of the data? No, you're seeing all the data sent. Chuck, what's the error code returned from each case? -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- 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/