X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.8 required=5.0 tests=AWL,BAYES_40,DKIM_SIGNED,DKIM_VALID,RCVD_IN_DNSWL_NONE,UNPARSEABLE_RELAY X-Spam-Check-By: sourceware.org X-Yahoo-SMTP: jenXL62swBAWhMTL3wnej93oaS0ClBQOAKs8jbEbx_o- Date: Thu, 13 Oct 2011 09:01:44 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: /proc/*/cmdline corrupted Message-ID: <20111013130144.GB15609@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <32645081 DOT post AT talk DOT nabble DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <32645081.post@talk.nabble.com> User-Agent: Mutt/1.5.20 (2009-06-14) 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 On Thu, Oct 13, 2011 at 05:55:41AM -0700, jan.kolar wrote: > > >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. If /proc//cmdline is shown to be corrupted it certainly is a topic for this list. As always a simple test case would allow us to debug the problem. cgf -- 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