| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 509.1 | how about... | VIDEO::OSMAN | type video::user$7:[osman]eric.six | Thu Jul 02 1987 16:10 | 9 |
| Well, I've got a program that will turn on the "debugging" bit in any
.EXE file. Then, you can do something like:
$ run/debug mumble
dbg> set out log
dbg> set log mumble.log
dbg> show symbol/all ! or is it "show symbol *", I forget
/Eric
|
| 509.2 | I use LIBR for that. | CASEE::VANDENHEUVEL | Formerly known as BISTRO::HEIN | Fri Jul 03 1987 03:51 | 4 |
| Another good hack is to put the image in an image library with
the librarian. Then ask the librarian to /LIST/NAMES.
Hein.
|
| 509.3 | Building .STB file | ILO::LENIHAN | | Fri Jul 03 1987 08:27 | 19 |
| Thanks,
There is no problem to see what symbols are in the shareable
image. All I do is
$ ANAL/IMAGE/NOHEAD/OUT=SYM <Shareable>.EXE
and then
$ SEAR SYM.ANL "symbol"/window=(1,1)
Thats fine!
What I'm really after is to rebuild the symbol table from the shareable
image. The LINKER reference states that a symbol table is appended
to the back of the shareable image. Can any wizards out there tell
me how to extract this into a .STB file.
Thanks in advance
john.
|
| 509.4 | Building an .STB file | BEAGLE::MOSER | | Wed Aug 12 1987 12:31 | 9 |
|
re: .3
To get a symbol table from an image just use the LINK qualifier
/SYMBOL and you'll have your own .STB file
$ LINK/SYMBOL=<filespec>/.... .....
-cmos-
|
| 509.5 | It's there, modules exist to get at it.. | MDVAX3::COAR | A wretched hive of bugs and flamers. | Mon Dec 14 1987 16:45 | 13 |
| But he said he didn't have the .OBJ file.
That symbol table information is what gets put in a SHAREABLE IMAGE
SYMBOL TABLE library (LIBRARY /SHARE), so there should be some way
of extracting it from something like that - however, I can't find
it. So, in the meantime, how about creating a temporary shareable
library with LIBRARY /SHARE /CREATE FOO BAR.EXE, and linking against
FOO? Or doing whatever it is you want to do against FOO? LIBRARY
/SHARE /LIST /NAMES /FULL should tell you anything you need to know
about the symbols therein, although not in a format easily usable
by a programme..
#ken :-)}
|