Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <42065DCC.4030606@x-ray.at>
Date: Sun, 06 Feb 2005 19:11:24 +0100
From: Reini Urban <rurban AT x-ray DOT at>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.7) Gecko/20040616
MIME-Version: 1.0
To: cygwin <cygwin AT cygwin DOT com>
Subject: Re: perl winpid?
References: <42065552 DOT 4050504 AT x-ray DOT at>
In-Reply-To: <42065552.4050504@x-ray.at>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Reini Urban schrieb:
> I feel quite stupid now, but found nothing simple.
> How to get the winpid from the current process in cygwin's perl?
> 
> $$ is the cygwin pid which is different from the windows pid 
> GetCurrentProcessId().
> Im just finishing perl-linwin32, and this is the last failing test, 
> assuming $$ == WINPID
> 
> Is GetCurrentProcessId() somewhere in Win32CORE or should I add it to 
> Win32::Process?
> 
> Win32::API is unfortunately not in libwin32, where it would be a simple
> $GetCurrentProcessId = new Win32::API( "kernel32.dll", 
> "GetCurrentProcessId", [], N )

In the meantime I added it as patch in
   http://rt.cpan.org/NoAuth/Bug.html?id=11399

This will be in perl-libwin32-0.191-2, but I'll wait a bit longer for 
response.
We should provide a more generic cygwin pid => winpid translator, but in 
which namespace?
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

--
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/