Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: Sat, 1 Mar 2003 02:16:48 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com, binutils AT sources DOT redhat DOT com Subject: Re: Bug in dumper Message-ID: <20030301071648.GA18096@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: <3E5F0B61 DOT 1040003 AT corpit DOT ru> <20030301034959 DOT GA25781 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030301034959.GA25781@redhat.com> User-Agent: Mutt/1.5.1i On Fri, Feb 28, 2003 at 10:50:00PM -0500, Christopher Faylor wrote: >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 ' >>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. It's still strange. I've rebuilt dumper and the call to bfd-set_arch_mach goes off into random memory. I don't see how that can be but it's late so I'm probably missing something. 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/