X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RP_MATCHES_RCVD,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org Message-ID: <32645081.post@talk.nabble.com> Date: Thu, 13 Oct 2011 05:55:41 -0700 (PDT) From: "jan.kolar" To: cygwin AT cygwin DOT com Subject: Re: /proc/*/cmdline corrupted In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 The content /proc//cmdline is created by the proces itself, in a separate thread. Since you use memory intensive application (xterm -sl 20000) we can speculate it might be caused by memory corruption in xterm. Observe whether the processes with corrupted /proc//cmdline behave properly and try avoiding '-sl 20000' as a work-arround. Unless there is another application with the same problem, this is not a topic for this list, I think. -- View this message in context: http://old.nabble.com/-proc-*-cmdline-corrupted-tp32639066p32645081.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple