From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: stub.h & stub.exe
Date: 3 Jul 2003 10:43:08 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 22
Message-ID: <be11bs$ms2$1@nets3.rz.RWTH-Aachen.DE>
References: <bds45r$poi$1 AT saphir DOT jouy DOT inra DOT fr>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 1057228988 23426 137.226.32.75 (3 Jul 2003 10:43:08 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 3 Jul 2003 10:43:08 GMT
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Eric Wajnberg <wajnberg AT antibes DOT inra DOT fr> wrote:

> I am now getting regularly several files my_file.000, my_file.001,
> my_file.002, etc., all of about 390 ko.

Those are temporary files created by 'stubify.exe', I think.  That's
the program that turns the program image file created by the linker
into an executable runnable by DOS.

This points at some possible reasons:

1) Incompatible tool versions.  Make sure your djdev, gcc and binutils
   package versions are known to work together correctly.  If in doubt,
   report them here (send the actual contents of manifest/*.mft files),
   and/or the output of "dir manifest" from the DJGPP main directory.

2) Some security software running on your machine running amok.  If you
   have a virus scanner or other running on your machine, please test if
   you still get those orphan files while it's disabled.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.