DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=mS5Wp6kDStz7v/578/gS5R5W1MGqMcNUBb2K7xfBWRaKHnSM8Lk65
	ztn0Lj5vF3VqWEb6/2mIuR4+uhTmawb8l45OQX8jOxN23mnqweIZT12pTo9KS9vN
	/KVSNbc8Q2gr+WhweJDA5N2sOK3/pqP/1/1Wq013B4sMVvspCXfXPA=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Thu, 25 Jul 2013 14:08:28 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Process command lines for Cygwin processes no longer viewable in Windows task manager as of Cygwin 1.7.21
Message-ID: <20130725180828.GA791@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <51F08F9D.6020606@coverity.com> <20130725082814.GA5124@calimero.vinschen.de> <51F1265B.1040704@cwilson.fastmail.fm> <51F133E4.6040506@coverity.com> <20130725151050.GA6932@ednor.casa.cgf.cx> <20130725152135.GA7761@ednor.casa.cgf.cx> <51F147C7.6050206@coverity.com> <20130725171856.GB6019@ednor.casa.cgf.cx> <51F165FB.60300@coverity.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <51F165FB.60300@coverity.com>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Thu, Jul 25, 2013 at 01:52:59PM -0400, Tom Honermann wrote:
>On 07/25/2013 01:18 PM, Christopher Faylor wrote:
>> On Thu, Jul 25, 2013 at 11:44:07AM -0400, Tom Honermann wrote:
>>> On 07/25/2013 11:21 AM, Christopher Faylor wrote:
>>>> On Thu, Jul 25, 2013 at 11:10:50AM -0400, Christopher Faylor wrote:
>>>>> It's not strace that's broken.  That's just a simple fix to the DLL.
>>>>
>>>> Actually, nevermind.  It's not a bug.
>>>
>>> Could you elaborate?  Prior to 1.7.21, strace provided the command line.
>>>   As of 1.7.21 it doesn't.  That looks like a regression to me.
>>
>> The output that you're looking at says "Here's the command line that is
>> being passed to CreateProcess".  Since there is now no command line the
>> strace output is correct.
>
>How does that make it not a regression?  The information used to be 
>provided, now it isn't.

You're reporting a problem "process command lines for Cygwin process no
longer viewable..." The problem occurs because a bug was fixed in cygwin
which erroneously caused those lines to be filled out.  The strace
output was previously reporting those lines being filled out.  Now it is
correctly reporting that the lines are not filled out.  It is accurate.

If you were relying on strace to show you the concatenated argv output
then you can't do that anymore for cygwin processes.  Sorry.  You'll
have to get that information from the "build_argv" lines in the execed
process.

>From a user's perspective, I don't care what the implementation is.

And from a developer's point of view when a user is trying to look at
strace output and not understanding it, then that indicates to me that
they don't understand the underlying code.  strace in cygwin is much
more detailed than strace on linux.  It is mainly intended as a
developer's tool for people who understand the code.  It contains names
of functions and variable names and hexadecimal output indicating
addresses.  You have to know what this all means.

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