Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Wed, 18 Apr 2001 16:21:51 -0400 From: Christopher Faylor To: Christopher Faylor Subject: Re: dumper.exe doesn't work Message-ID: <20010418162151.M3648@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: Christopher Faylor References: <177347119581 DOT 20010418202024 AT logos-m DOT ru> <20010418153350 DOT L3648 AT redhat DOT com> <144359753848 DOT 20010418235058 AT logos-m DOT ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <144359753848.20010418235058@logos-m.ru>; from deo@logos-m.ru on Wed, Apr 18, 2001 at 11:50:58PM +0400 On Wed, Apr 18, 2001 at 11:50:58PM +0400, egor duda wrote: >Hi! > >Wednesday, 18 April, 2001 Christopher Faylor cgf AT redhat DOT com wrote: > >>>i don't think so. maybe gdb snapshots are built without cygwin core >>>dumps support? can you build gdb yourself and check? make sure that >>>configure finds sys/procfs.h and win32_pstatus_t in it. > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ only this, i think. > >CF> Is there something special that needs to be done to build a snapshot for >CF> core dump support? I wasn't aware of any special considerations for >CF> doing this. Sorry. My reading skills seem to be in need of repair this week. That's usually a sign of too little sleep or too much multitasking. In this case, it's both. AFAIK, the gdb snapshots should be built with core dump support. Wouldn't the error message be different if they weren't? Anyway, I'm building a snapshot right now to see if there is a glitch somewhere. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple