This is the mail archive of the
mailing list for the Cygwin project.
Re: /proc/*/cmdline corrupted
On Mon, Oct 17, 2011 at 12:47 PM, jan.kolar <firstname.lastname@example.org> 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
> 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
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple