Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date:	Fri, 28 Feb 2003 22:50:00 -0500
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com, binutils AT sources DOT redhat DOT com
Subject:	Re: Bug in dumper
Message-ID:	<20030301034959.GA25781@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com, binutils AT sources DOT redhat DOT com
References:	<Pine DOT LNX DOT 4 DOT 44 DOT 0302271156500 DOT 1192-100000 AT localhost DOT localdomain> <3E5F0B61 DOT 1040003 AT corpit DOT ru>
Mime-Version:	1.0
In-Reply-To:	<3E5F0B61.1040003@corpit.ru>
User-Agent:	Mutt/1.5.1i

On Fri, Feb 28, 2003 at 10:10:25AM +0300, Egor Duda wrote:
>This means that either i'm wrong about my assumptions about 
>bfd_set_arch_mach() and its return, or there's a bug in binutils. It 
>should be quite easy to debug, though, for those who have a cygwin 
>toolchain installed. Just build dumper with debug info (this will 
>require building bfd alongside), start any innocent process, say, bash, 
>get its pid and then run 'dumper -d c:/cygwin/bin/bash.exe <bash_pid>' 
>under gdb. This should reveal what status is returned by 
>bfd_set_arch_mach, and why.

I just tried this.  The release version of dumper.exe doesn't work.
The one I *just* built does.  Weird.

I'll see if I can track down what's going on.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -