X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.1 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: <32668723.post@talk.nabble.com> Date: Mon, 17 Oct 2011 09:47:16 -0700 (PDT) From: "jan.kolar" To: cygwin@cygwin.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@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com > Jon Clugston wrote: > I tried to reproduce by creating long command lines to other commands > and none were corrupted. I tried two now. The first one turned out to be a script around xterm. :-( The second fails the test: xwininfo.exe -display :0 -children & >>> tty0 00:00:00 xwininfo -children -children The third fails as well: xcalc -bg blue -fg green & >>> tty0 00:00:00 xcalc blue -fg green > Does "xterm" step on its command line? If it can it does. Now (!sorry) I remember seeing that in nineties. -- View this message in context: http://old.nabble.com/-proc-*-cmdline-corrupted-tp32639066p32668723.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