From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=-0.5 required=3.0 tests=BAYES_05 autolearn=ham
	autolearn_force=no version=3.4.5-pre1
Date: 11 Jul 91 20:11:46 GMT
From: sdd.hp.com!spool.mu.edu!news.cs.indiana.edu!uceng.uc.edu!cslusher@decwrl.
dec.com  (charles e slusher)
Subject: Static sizes
Message-ID: <1991Jul11.201146.2843@uceng.UC.EDU>
List-Id: <comp.lang.ada>

Hello,

   I am trying to find static size information about some Vax Ada 
   executables.  I have the linker maps with a cross reference table
   and the addresses from the SHOW SYM/ADDR * command in the debugger.
   Apparently the library modules (like text_io) are not loaded 
   contiguously so I can't use the addresses to determine size.  Am I
   right in this?  I am looking for the sizes of everything including
   libraries (to see how much they cost me to bring in).  I am assuming
   that this will all add up relatively close the directory listing 
   size of the .exe file.  The ANALYSE/IMAGE command gives too little
   information and compiling with the MACHINE_CODE option doesn't give 
   listing for the components brought in by the linker.

   As a point of reference, I did this all in Unix (Verdix Ada) using
   the nm -n command and the adb debugger.  I am now in the position
   of needing to do this on a Vax (to which I am fairly new).  The grey
   wall of manuals is somewhat forbidding, and so far has not yielded
   up to me the information I need.

   Can I get detailed sizing info from VMS?  
   Will the sizes of all the elements in the symbol table add up reasonably 
   to the .exe file?  
   Does Vax Ada work differently from what I am used to with Verdix on the Sun?

   You can respond with email if you wish to:  ces@thor.ece.uc.edu


   Thanks for any enlightenment,

   Charles Slusher