On 07/26/2013 01:58 PM, Tom Honermann wrote:
On 07/26/2013 01:38 PM, Christopher Faylor wrote:
On Thu, Jul 25, 2013 at 02:16:04PM -0400, Christopher Faylor wrote:
On Thu, Jul 25, 2013 at 09:21:31AM -0400, Charles Wilson wrote:
On 7/25/2013 4:28 AM, Corinna Vinschen wrote:
On Jul 24 22:38,
On Tue, Jul 30, 2013 at 01:52:05PM -0400, Tom Honermann wrote:
On 07/26/2013 01:58 PM, Tom Honermann wrote:
On 07/26/2013 01:38 PM, Christopher Faylor wrote:
On Thu, Jul 25, 2013 at 02:16:04PM -0400, Christopher Faylor wrote:
On Thu, Jul 25, 2013 at 09:21:31AM -0400, Charles Wilson wrote:
On
On Thu, Jul 25, 2013 at 02:16:04PM -0400, Christopher Faylor wrote:
On Thu, Jul 25, 2013 at 09:21:31AM -0400, Charles Wilson wrote:
On 7/25/2013 4:28 AM, Corinna Vinschen wrote:
On Jul 24 22:38, Tom Honermann wrote:
My suspicion that this started with 1.7.21 is based on Corinna's
comments in
On 07/26/2013 01:38 PM, Christopher Faylor wrote:
On Thu, Jul 25, 2013 at 02:16:04PM -0400, Christopher Faylor wrote:
On Thu, Jul 25, 2013 at 09:21:31AM -0400, Charles Wilson wrote:
On 7/25/2013 4:28 AM, Corinna Vinschen wrote:
On Jul 24 22:38, Tom Honermann wrote:
My suspicion that this
On 07/25/2013 02:15 PM, Buchbinder, Barry (NIH/NIAID) [E] wrote:
Tom Honermann sent the following at Thursday, July 25, 2013 1:53 PM
Does this (or a variation thereof) do what you want?
c:\cygwin\bin\procps -A --format cmd
Thank you for the suggestion, but no. My use case really does
On Jul 24 22:38, Tom Honermann wrote:
It seems that process command lines for Cygwin processes are no
longer viewable in Windows task manager, SysInternals Process
Explorer, or other similar tools. I suspect, but have not verified,
that this change occurred with the Cygwin 1.7.21 release.
On 7/25/2013 4:28 AM, Corinna Vinschen wrote:
On Jul 24 22:38, Tom Honermann wrote:
My suspicion that this started with 1.7.21 is based on Corinna's
comments in http://cygwin.com/ml/cygwin/2013-07/msg00343.html and
other anecdotal evidence of new problems occurring as of that
release.
This is
On 07/25/2013 09:21 AM, Charles Wilson wrote:
On 7/25/2013 4:28 AM, Corinna Vinschen wrote:
On Jul 24 22:38, Tom Honermann wrote:
My suspicion that this started with 1.7.21 is based on Corinna's
comments in http://cygwin.com/ml/cygwin/2013-07/msg00343.html and
other anecdotal evidence of new
On Thu, Jul 25, 2013 at 10:19:16AM -0400, Tom Honermann wrote:
On 07/25/2013 09:21 AM, Charles Wilson wrote:
On 7/25/2013 4:28 AM, Corinna Vinschen wrote:
On Jul 24 22:38, Tom Honermann wrote:
My suspicion that this started with 1.7.21 is based on Corinna's
comments in
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.
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
On 07/25/2013 11:10 AM, Christopher Faylor wrote:
On Thu, Jul 25, 2013 at 10:19:16AM -0400, Tom Honermann wrote:
On 07/25/2013 09:21 AM, Charles Wilson wrote:
On 7/25/2013 4:28 AM, Corinna Vinschen wrote:
On Jul 24 22:38, Tom Honermann wrote:
My suspicion that this started with 1.7.21 is
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
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
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
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:
On Thu, Jul 25, 2013 at 09:21:31AM -0400, Charles Wilson wrote:
On 7/25/2013 4:28 AM, Corinna Vinschen wrote:
On Jul 24 22:38, Tom Honermann wrote:
My suspicion that this started with 1.7.21 is based on Corinna's
comments in http://cygwin.com/ml/cygwin/2013-07/msg00343.html and
other anecdotal
Tom Honermann sent the following at Thursday, July 25, 2013 1:53 PM
Does this (or a variation thereof) do what you want?
c:\cygwin\bin\procps -A --format cmd
- Barry
Disclaimer: Statements made herein are not made on behalf of NIAID.
--
Problem reports: http://cygwin.com/problems.html
It seems that process command lines for Cygwin processes are no longer
viewable in Windows task manager, SysInternals Process Explorer, or
other similar tools. I suspect, but have not verified, that this change
occurred with the Cygwin 1.7.21 release. Process command lines do
appear as
18 matches
Mail list logo
