Date:	Tue, 9 Jan 2001 10:03:54 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	"Peter J. Farley III" <pjfarley AT banet DOT net>
cc:	djgpp-workers AT delorie DOT com, Martin Str|mberg <ams AT ludd DOT luth DOT se>,
	ceo AT nbensacomputers DOT com
Subject:	Re: Fw: Patch for statfs.c
In-Reply-To:	<5.0.2.1.0.20010108231043.03469460@pop5.banet.net>
Message-ID:	<Pine.SUN.3.91.1010109100325.19017D-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, 8 Jan 2001, Peter J. Farley III wrote:

>  >Since two versions of statfs which are supposed to be identical return
>  >different values, I think the only way to find out why is to step inside
>  >
>  >both versions with a debugger and see where does the difference come
>  >from.  Perhaps there's some bug in how the transfer buffer is layed out
>  >when passing requests to the CDROM driver vie Int 2Fh.
> 
> Could it be that fil316b.zip was built with the older version of statfs 
> that is packaged in the fil316s.zip archive (which might explain the 
> difference)?

Does the version in fil316s.zip differ from what's in stock v2.03
libc?  If so, it's possible that you are right (I didn't build the
current fil316b.zip on SimTel, so I don't know for sure).

In any case, I think we need to understand the cause for the
discrepancy, because it might provide us with the solution to the
problem of slightly incorrect size.

> Can objdump be used to extract just one function's code from an 
> executable?

What do you mean by that?  Do you want to see the disassembly of a
single function?

> If we could extract just the statfs function, we could 
> diff the output of objdump of the statfs code from the distributed 
> binary and the current libc version of statfs to see how they are 
> different.

That won't be easy, I'm afraid: differences in compiler and Binutils
versions and switches can produce changes on the assembly level that
completely obscure the real code differences.

It is much easier to try several avaiable versions of statfs, since
the number of these versions is small (like 3 or something).

- Raw text -