stub.h & stub.exe

stub.h & stub.exe

Post by Eric Wajnbe » Wed, 02 Jul 2003 23:00:28



Dear all,

I recently upgraded to the lastest djgpp version, on Windows 98.

I am developing a C-code in a file my_file.c, leading to a my_file.exe.

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

In it, it is written things like:

stub.h generated from stub.asm by djasm, on Mon Dec 24 21:21:52 2001
The STUB.EXE stub loader is Copyright (C) 1993-1995 DJ Delorie.
Permission granted to use for any purpose provided this copyright
remains present and unmodified.
This only applies to the stub, and not necessarily the whole program.

etc...

What are these files? How I can get rid of them? What are these stub.h &
stub.exe?

Thanks for any help on that.

best, Eric.

 
 
 

stub.h & stub.exe

Post by Martin Strombe » Fri, 04 Jul 2003 18:45:15


: I recently upgraded to the lastest djgpp version, on Windows 98.

: I am developing a C-code in a file my_file.c, leading to a my_file.exe.

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

And your .EXE is ca 390kB too, right?

: In it, it is written things like:

: stub.h generated from stub.asm by djasm, on Mon Dec 24 21:21:52 2001
: The STUB.EXE stub loader is Copyright (C) 1993-1995 DJ Delorie.
: Permission granted to use for any purpose provided this copyright
: remains present and unmodified.
: This only applies to the stub, and not necessarily the whole program.
: $Id: stub.asm built 12/24/01 21:21:52 by djasm $

: etc...

: What are these files? How I can get rid of them? What are these stub.h &
: stub.exe?

If you add "-v" to gcc's command line you will see them being
generated.

They are temporary files made during the last stage of generating an
.EXE when the programs are prepended the stub that make them DOS .EXE
files.

They should normally automatically be removed. Which versions of GCC
and DJGPP (include the date on libc.a too) are you using?

Right,

                                                MartinS

 
 
 

stub.h & stub.exe

Post by Hans-Bernhard Broeke » Fri, 04 Jul 2003 19:43:08



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

Even if all the snow were burnt, ashes would remain.

 
 
 

stub.h & stub.exe

Post by Eric Wajnbe » Fri, 04 Jul 2003 20:40:11



: : I recently upgraded to the lastest djgpp version, on Windows 98.

: : I am developing a C-code in a file my_file.c, leading to a my_file.exe.

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

: And your .EXE is ca 390kB too, right?

: : In it, it is written things like:

: : stub.h generated from stub.asm by djasm, on Mon Dec 24 21:21:52 2001
: : The STUB.EXE stub loader is Copyright (C) 1993-1995 DJ Delorie.
: : Permission granted to use for any purpose provided this copyright
: : remains present and unmodified.
: : This only applies to the stub, and not necessarily the whole program.
: : $Id: stub.asm built 12/24/01 21:21:52 by djasm $

: : etc...

: : What are these files? How I can get rid of them? What are these stub.h &
: : stub.exe?

: If you add "-v" to gcc's command line you will see them being
: generated.

Ok, but I am not using "-v" to compile my code.

: They are temporary files made during the last stage of generating an
: .EXE when the programs are prepended the stub that make them DOS .EXE
: files.

: They should normally automatically be removed. Which versions of GCC
: and DJGPP (include the date on libc.a too) are you using?

I do not know exactly where I can see what version I'm using. I collect this
from a file gcc323b.zip and the libc.a as a date of 24/12/01.

Thanks for your answer, anyway.

Best, Eric.

 
 
 

stub.h & stub.exe

Post by Eric Wajnbe » Fri, 04 Jul 2003 20:42:43



: : I recently upgraded to the lastest djgpp version, on Windows 98.

: : I am developing a C-code in a file my_file.c, leading to a my_file.exe.

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

: And your .EXE is ca 390kB too, right?

: : In it, it is written things like:

: : stub.h generated from stub.asm by djasm, on Mon Dec 24 21:21:52 2001
: : The STUB.EXE stub loader is Copyright (C) 1993-1995 DJ Delorie.
: : Permission granted to use for any purpose provided this copyright
: : remains present and unmodified.
: : This only applies to the stub, and not necessarily the whole program.
: : $Id: stub.asm built 12/24/01 21:21:52 by djasm $

: : etc...

: : What are these files? How I can get rid of them? What are these stub.h &
: : stub.exe?

: If you add "-v" to gcc's command line you will see them being
: generated.

Ok, but I am not using "-v" to compile my code.

: They are temporary files made during the last stage of generating an
: .EXE when the programs are prepended the stub that make them DOS .EXE
: files.

: They should normally automatically be removed. Which versions of GCC
: and DJGPP (include the date on libc.a too) are you using?

I do not know where I can see the version I am using. I collect this (among
other things) from a file gcc323b.zip, and the libc.a as a date of 24/12/01.

Thanks for your answers anyway.

Best, Eric.

 
 
 

stub.h & stub.exe

Post by Hans-Bernhard Broeke » Fri, 04 Jul 2003 20:56:41



> : If you add "-v" to gcc's command line you will see them being
> : generated.
> Ok, but I am not using "-v" to compile my code.

A misunderstanding.  Martin wanted to suggest that you *should* try it
with -v once in a while, to see what exactly happens during your
compilation.  -v is a debugging aid, using it might help you see
through problems like this.

Quote:> : They should normally automatically be removed. Which versions of GCC
> : and DJGPP (include the date on libc.a too) are you using?
> I do not know exactly where I can see what version I'm using.

By using that '-v' flag, among other ways.

The version of binutils may be important for this, too.  What does

        ld -v

print?  And/or what do you get if you type

        dir c:\djgpp\manifest

(change pathname of DJGPP installation director if it's not c:\djgpp)
--

Even if all the snow were burnt, ashes would remain.

 
 
 

stub.h & stub.exe

Post by Eric Wajnbe » Fri, 04 Jul 2003 20:57:42



: > 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.

I do not think this is the explanation. I install all of these files the same
day using the "zip picker" on the djgpp web site.

: 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.

No security softwares running permanently on my machine.

The strange thing is that I am not getting those files all the times. Most of
the time, I do not have them.

Anyway, what I understand is that I can delete them without any problem, and
there are not appearing because there are problems in my code. This is already
something important (for me).

Thanks, anyway.

Best, Eric.

 
 
 

stub.h & stub.exe

Post by Eric Wajnbe » Fri, 04 Jul 2003 21:03:59



: > : If you add "-v" to gcc's command line you will see them being
: > : generated.

: > Ok, but I am not using "-v" to compile my code.

: A misunderstanding.  Martin wanted to suggest that you *should* try it
: with -v once in a while, to see what exactly happens during your
: compilation.  -v is a debugging aid, using it might help you see
: through problems like this.

: > : They should normally automatically be removed. Which versions of GCC
: > : and DJGPP (include the date on libc.a too) are you using?

: > I do not know exactly where I can see what version I'm using.

: By using that '-v' flag, among other ways.

Ok, I am running gcc version 3.2.3

: The version of binutils may be important for this, too.  What does

:       ld -v

The answer is GNU ls version 2.13

: print?  And/or what do you get if you type

:       dir c:\djgpp\manifest

The answer is:

.              <REP>        20/05/03  11:16 .
..             <REP>        20/05/03  11:16 ..
DJDEV203 MFT         2 957  04/12/01  20:57 djdev203.mft
DJDEV203 DSM           827  10/03/02  22:32 djdev203.dsm
DJDEV203 VER            57  10/06/02  23:49 djdev203.ver
FAQ230B  MFT           135  21/01/00  18:28 faq230b.mft
FAQ230B  VER            53  21/01/00  18:28 faq230b.ver
RHID14~1 MFT         1 010  10/02/00  12:14 rhid1475b.mft
RHID14~1 VER            40  10/02/00  12:14 rhid1475b.ver
BNU213B  DSM           765  15/08/02  10:34 bnu213b.dsm
BNU213B  MFT         1 521  15/08/02  10:48 bnu213b.mft
BNU213B  VER            52  15/08/02  10:34 bnu213b.ver
GCC323B  DSM         1 085  30/04/03  19:10 gcc323b.dsm
GCC323B  MFT         1 944  30/04/03  19:11 gcc323b.mft
GCC323B  VER            56  30/04/03  19:10 gcc323b.ver
GDB53B   DSM         2 387  12/01/03  11:02 gdb53b.dsm
GDB53B   VER            46  12/01/03  11:01 gdb53b.ver
GDB53B   MFT           472  27/12/02  16:16 gdb53b.mft
MAK3791B MFT           305  14/07/00  15:24 mak3791b.mft
MAK3791B VER            51  14/07/00  15:18 mak3791b.ver
MAK3791B DSM         1 769  26/07/00   7:39 mak3791b.dsm
TXI42B   MFT         1 163  03/04/02  12:03 txi42b.mft
TXI42B   DSM         1 460  03/04/02  12:18 txi42b.dsm
TXI42B   VER            46  03/04/02  12:19 txi42b.ve

Best, Eric.

 
 
 

1. what's the size of the DJGPP stub + .EXE header?

I need to know the size of the DJGPP stub plus the .EXE header.  In most
compilers, to get a flat binary file, you simply strip the first 512
bytes (which would be the .EXE header) from the resultant executable.

In DJGPP you can't do this though because of the stub (correct?), so I
need to know the size of the stub, so that I can strip it from the
executable to get a flat binary file.

Thanks,
Jeff

--------------------------------------------
            - Code X Software -
       Programming to a Higher Power


  web:   http://www.execulink.com/~pweeks/
--------------------------------------------

2. Any satellte interface for Cisco

3. GDB Remote & 386 stub

4. Eines Bild an einer Seite anpassen...

5. remote debug stub and Windows 2000

6. Emacs takes long time to load

7. Stubs - definition

8. Alpha/VMS V Sun/Solaris

9. ANNOUNCE: GDB stub for remote debugging of DJGPP targets

10. stub ?

11. Stubbing a Program?

12. Buggy Symlinks (Bug in stub.asm)

13. Help: GDB remote debugging stub i386