X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Date: Fri, 24 Apr 2009 00:57:17 +0200 To: cygwin AT cygwin DOT com Subject: Re: pstree on windows xp - find process spawned from windows process From: "Matthias Andree" Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8 MIME-Version: 1.0 References: <23197461 DOT post AT talk DOT nabble DOT com> <49F0B2B9 DOT 7000804 AT cygwin DOT com> <23205009 DOT post AT talk DOT nabble DOT com> <49F0E6B3 DOT 7030607 AT cygwin DOT com> Content-Transfer-Encoding: 7bit Message-ID: In-Reply-To: <49F0E6B3.7030607@cygwin.com> User-Agent: Opera Mail/9.64 (Linux) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Am 24.04.2009, 00:07 Uhr, schrieb Larry Hall (Cygwin) : > nachum wrote: >>>> Hi, I'm new to cygwin, and I am beginning to like it. I am having >>>> trouble >>>> though with child processes that have only Windows PIDs and not cygwin >>>> PIDs. >>>> >>>> When I run Xilinx bitgen from cygwin 2 processes are run both with the >>>> name >>>> bitgen.exe. Below I am running bitgen through make. >>>> >>>> PID PPID PGID WINPID TTY UID STIME COMMAND >>>> S 3936 2836 3936 2380 0 12696 19:54:49 /usr/bin/make >>>> S 808 3936 3936 2852 0 12696 19:54:49 >>>> /cygdrive/c/Xilinx/10.1/ISE/bin/nt/bitgen >>>> 2852 0 0 2852 ? 0 19:54:49 >>>> c:\Xilinx\10.1\ISE\bin\nt\bitgen.exe >>>> 504 0 0 504 ? 0 19:54:49 >>>> c:\Xilinx\10.1\ISE\bin\nt\unwrapped\bitgen.exe > Since I'm not sure what Xilinx is doing, I can't really say. Someone > else > here *might* be able to tell you, if they have run into the same thing > either with Xilinx or some other native Windows app. But since this > probably has more to do with Xilinx's particular implementation and less > to do with Cygwin proper, this would be off-topic for this list. That's > one of the reasons why I was suggesting talking to the Xilinx folks. > That > and the fact that they should know exactly what they're doing, why, and > how you might track it. Not entirely - the problem being that pstree always uses Cygwin PIDs which are not necessarily the same as WINPIDs - it would be quite useful if pstree had an option to display Windows PIDs. (In fact, I had to rewrite the PIDs in my pstree output of the git-svn report on this list some hours earlier to the winpids to match the sysinternals handle output...) -- Matthias Andree -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/