* Static sizes
@ 1991-07-11 20:11 charles e slusher
0 siblings, 0 replies; only message in thread
From: charles e slusher @ 1991-07-11 20:11 UTC (permalink / raw)
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~1991-07-11 20:11 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1991-07-11 20:11 Static sizes charles e slusher
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox