Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Message-ID: <3D57C88D.1090406@hekimian.com> Date: Mon, 12 Aug 2002 10:39:09 -0400 X-Sybari-Trust: 07839f78 b923d9bf 4738785c 00000109 From: Joe Buehler Reply-To: joseph DOT buehler AT spirentcom DOT com Organization: Spirent Communications User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Conrad Scott CC: cygwin-developers AT cygwin DOT com Subject: Re: SIGCLD (?) problem References: <016a01c24148$e61594e0$6132bc3e AT BABEL> <20020811192301 DOT GA9017 AT redhat DOT com> <004101c24194$734d82a0$6132bc3e AT BABEL> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Conrad Scott wrote: > BTW I don't know how (i.e. I haven't bothered to find out how) to > convert these system DLL addresses into function names, so I hope > this is of some use. You can get some info with "dumpbin /exports" on the dll itself. A full symbol list for NT symbols can be had from the dbg files that Microsoft supplies. I believe I used "nm" on them. Unfortunately, XP symbols are in a different format that nm does not understand. Joe Buehler