X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.1 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
In-Reply-To:	<32668723.post@talk.nabble.com>
References:	<CAG_2cT=rmeJpmZbYDo7RAwjNcTTDSTH1SMhuzzL9qi09ZJwGyA AT mail DOT gmail DOT com> <CAG_2cTmn8+ZQSyu2YAxW2vLJQ+MF-xuXw11sZen6otTCaKvyKw AT mail DOT gmail DOT com> <32668723 DOT post AT talk DOT nabble DOT com>
Date:	Mon, 17 Oct 2011 19:28:55 -0400
Message-ID:	<CAG_2cT=aA2MtvLu-6Z81Mo+N2obRiRB8F47RjzJgNYmEokD1Lg@mail.gmail.com>
Subject:	Re: /proc/*/cmdline corrupted
From:	Jon Clugston <jon DOT clugston AT gmail DOT com>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id p9HNTFVD014814

On Mon, Oct 17, 2011 at 12:47 PM, jan.kolar <kolar AT math DOT cas DOT cz> wrote:
>
>
>> 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.

From some light code inspection on my part and more thorough
investigation from others here, it seems to be the X libraries
mangling the command lines of any X program that calls them (when they
use common parameters).  I would say this is a bug in the X libraries.
 I wouldn't expect cygwin to try to prevent this dubious practice by
application code.


Jon

> --
> 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
>
>

--
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

- Raw text -