This is the mail archive of the
mailing list for the Cygwin project.
Re: Bug in dumper
- From: Christopher Faylor <cgf at redhat dot com>
- To: cygwin at cygwin dot com, binutils at sources dot redhat dot com
- Date: Sat, 1 Mar 2003 02:16:48 -0500
- Subject: Re: Bug in dumper
- References: <Pine.LNX.email@example.com> <3E5F0B61.firstname.lastname@example.org> <20030301034959.GA25781@redhat.com>
- Reply-to: cygwin at cygwin dot com
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 <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.
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.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html