Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Date: 22 Jan 2002 13:43:16 -0500
Message-ID: <20020122184316.25503.qmail@lizard.curl.com>
From: Jonathan Kamens <jik AT curl DOT com>
To: cygwin-developers AT cygwin DOT com
CC: cygwin-developers AT cygwin DOT com
In-reply-to: <192230668183.20020115145735@logos-m.ru> (message from egor duda
	on Tue, 15 Jan 2002 14:57:35 +0300)
Subject: Re: Am I using dumper.exe correctly?
References: <20020110214350 DOT 30413 DOT qmail AT lizard DOT curl DOT com>
 <380850877 DOT 20020111104002 AT logos-m DOT ru>
 <20020114175405 DOT 9881 DOT qmail AT lizard DOT curl DOT com>
 <96167013072 DOT 20020114211637 AT logos-m DOT ru>
 <20020114214629 DOT 22496 DOT qmail AT lizard DOT curl DOT com> <192230668183 DOT 20020115145735 AT logos-m DOT ru>

>  Date: Tue, 15 Jan 2002 14:57:35 +0300
>  From: egor duda <deo AT logos-m DOT ru>
>  
>  can you please try this patch, rebuild gdb, ensuring that it uses
>  latest w32api headers, and give it a try?

Yes, that patch did the trick.

Now I suppose I need to convince cgf, who appears to be the maintainer
of the gdb package, to release a new gdb package with this fix in it
:-).

Thanks,

  jik