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: Sat, 1 Mar 2003 19:12:50 +0100 (CET)
From: Ronald Landheer-Cieslak <ronald AT landheer DOT com>
X-X-Sender: ronald AT localhost DOT localdomain
To: cygwin AT cygwin DOT com
cc: binutils AT sources DOT redhat DOT com
Subject: Re: Bug in dumper
In-Reply-To: <20030228220426.GE14769@redhat.com>
Message-ID: <Pine.LNX.4.44.0303011900520.27345-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Just to set the record straight: none of the text I wrote is still in the
mail below - yet my name is?

Anyways, dumper works fine for me (on an NT/4 box with all the latest), 
which is what I told the original poster. I also told him to take a closer 
look at the exit code of dumper.

I just don't like being mis-quoted :|

rlc

 On Fri, 28 Feb 2003, Christopher Faylor wrote: 
> On Fri, Feb 28, 2003 at 10:10:25AM +0300, Egor Duda wrote:
> >Ronald Landheer-Cieslak wrote:
> >>>Does dumper.exe work?
> >
> >Well, i should have answered this, but unfortunately, i have no access 
> >to windows machine right now to debug, or even verify this.
> >
> >>>Upon execution I see the following in the cygwin console:
> >>> $ ./div.exe
> >>>       7 [main] div 2296 handle_exceptions: Error while dumping state 
> >>>       (probably corrupted stack)
> >>> Arithmetic exception (core dumped)
> >>>
> >>>In the cmd.exe console window that dumper.bat starts I see the following:
> >>> C:\cygwin\home\jlambert>dumper.exe -d C:/cygwin/home/jlambert/div.exe 
> >>> 1884
> >>> dumping process #1884 to div.exe.core
> >>> setting bfd architecture: No error
> >
> >Well, this is a strange line. This last line of dumper's output 
> >indicates than call to bfd_set_arch_mach(abfd, bfd_arch_i386, 0) havs 
> >returned non-zero status, which should indicate an error (if i 
> >understand things correctly), yet bfd_perror called immediately 
> >afterwards has printed "No error" message.
> >
> >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.
> 
> Unless someone beats me to this, I'll take a look at this tonight EST.
> 
> 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/
> 


--
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/