On Apr 24 00:27, nachum wrote:
> Regarding forking - you can see from my first post that bitgen is spawning a
> new process / PID and there is no way that I've found within cygwin to
> identify which program is the parent of the new fork. PID 504 is the new
Sure. It's a native Windows process, no
ent of the new fork. PID 504 is the new
forked bitgen, and it has 0s for the PPID and PGID entries. The original
bitgen process appears twice under ps -W and they are clearly the same
process as can be seen from the WINPID in both processes. The reason I want
to know programmatically who the parent
Matthias Andree wrote:
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 processe
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 th
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.
n to do the
actual processing. This means I need a programmatic way of saying this is
the PID that belongs to this instance of make->bitgen. pstree doesn't seem
to allow identifying Windows sub processes, if I could do that then I could
use pstree to figure out which bitgen is s
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.
a name based kill of bitgen b/c that will kill all bitgens that
might be going on at the same time.
I am running in an xterm on XP 32 bit SP3. Here are some relevant versions:
bash 3.2.48(21)
ps 1.11
pstree 21.5
kill 1.14
thanx,
nachum
--
View this message in context:
http://www.nabble.com/pstree-
8 matches
Mail list logo