X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Trace-PostClient-IP: 68.147.131.211
From: Brian Inglis <Brian DOT Inglis AT SystematicSW DOT Invalid>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: cp.exe bug
Organization: Systematic Software
Message-ID: <va3tj0haotngqqneg4n5uoij5ve293i1vu@4ax.com>
References: <h6b_c.15664$Xd6 DOT 1977 AT newssvr29 DOT news DOT prodigy DOT com> <01c4929c$Blat.v2.2.2$92cbcdc0 AT zahav DOT net DOT il> <Rnp_c.15879$sf2 DOT 1615 AT newssvr27 DOT news DOT prodigy DOT com> <01c49300$Blat.v2.2.2$e967e600 AT zahav DOT net DOT il> <p_c%c.12596$QJ3 DOT 4005 AT newssvr21 DOT news DOT prodigy DOT com> <01c4950a$Blat.v2.2.2$00dfe020 AT zahav DOT net DOT il> <%pu%c.17242$LU2 DOT 11171 AT newssvr27 DOT news DOT prodigy DOT com> <01c49556$Blat.v2.2.2$2dc619a0 AT zahav DOT net DOT il>
X-Newsreader: Forte Agent 1.93/32.576 English (American)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 34
Date: Wed, 08 Sep 2004 04:44:30 GMT
NNTP-Posting-Host: 24.71.223.147
X-Complaints-To: abuse AT shaw DOT ca
X-Trace: pd7tw3no 1094618670 24.71.223.147 (Tue, 07 Sep 2004 22:44:30 MDT)
NNTP-Posting-Date: Tue, 07 Sep 2004 22:44:30 MDT
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

On Wed, 08 Sep 2004 06:43:41 +0300 in comp.os.msdos.djgpp, "Eli
Zaretskii" <eliz AT gnu DOT org> wrote:

>> From: "one2001boy AT yahoo DOT com" <one2001boy AT yahoo DOT com>
>> Date: Wed, 08 Sep 2004 02:48:27 GMT
>> 
>> Eli Zaretskii wrote:
>> >>From: "one2001boy AT yahoo DOT com" <one2001boy AT yahoo DOT com>
>> >>Date: Tue, 07 Sep 2004 06:58:29 GMT
>> >>
>> >>I need to uninstall the old version of djgpp first and reinstall
>> >>the latest version.
>> > 
>> > What for?  You should be able to debug the program no matter what
>> > version of DJGPP you have installed.
>> 
>> The alhpa version of cp.exe works fine (no need to debug).
>> 
>> Only the beta version of cp.exe has the problem. The source code for 
>> cp.exe for both alpha and beta is the same, thus the glibc etc needs to 
>> be updated. Right?
>
>We are talking about finding out where in cp the bug happens.  For
>this, you only need to establish what line in cp's sources fails to
>work.  You don't need to go into the library function's code.

ISTM OP's saying he's running the alpha code and can't reproduce the
problem, so he needs to load the beta code to reproduce the problem. 

-- 
Thanks. Take care, Brian Inglis 	Calgary, Alberta, Canada

Brian DOT Inglis AT CSi DOT com 	(Brian[dot]Inglis{at}SystematicSW[dot]ab[dot]ca)
    fake address		use address above to reply