X-Recipient: archive-cygwin@delorie.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@mail.gmail.com>	<CAG_2cTmn8+ZQSyu2YAxW2vLJQ+MF-xuXw11sZen6otTCaKvyKw@mail.gmail.com>	<32668723.post@talk.nabble.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.clugston@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=ISO-8859-1
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Content-Transfer-Encoding: 8bit
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@math.cas.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


