Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!apple!usc!elroy.jpl.nasa.gov!ncar!noao!coyote!jmh
From: jmh@coyote.uucp (John Hughes)
Newsgroups: comp.sys.tandy
Subject: Need Info on Xenix xexec header
Message-ID: <1991Jan21.185659.4800@coyote.uucp>
Date: 21 Jan 91 18:56:59 GMT
Organization: Datalog Consulting, Tucson, AZ
Lines: 35



Here's one for the Tandy Xenix gurus:

I'm trying to read, and possibly dissassemble, object (*.o) files
for Tandy Xenix. So far, I have the code to read the header
structure, the symbol and relocation tables, and an opcode table
for the 68000. But I'm having a problem with the file format.

Does anyone happen to know how the loader determines the size, if
any, of ASCII text strings lurking between a binary file header
and the actual start of the text area? I know this is probably
a stupid question to those in the know, but, I have just about
thumbed my dev. sys. manuals to death, and still can't find any
useful information about it. Am I looking at the info, but just
not understanding it? (That's very possible)

All I need to do is compute the actual start point, from the 
beginning of the binary file, of the text area. I have (I think..)
the rest of it pretty much nailed (then again, maybe not).

Thanks in advance.

-John

(it never ceases to amaze me how an inanimate object composed of
plastic, silicon, and metal can make me feel so damn stupid :-| )



-- 
|     John M. Hughes      | "...unfolding in consciousness at the            |
| noao!jmh%moondog@coyote | deliberate speed of pondering."  - Daniel Dennet |
| jmh%coyote@noao.edu     |--------------------------------------------------|
| noao!coyote!jmh         | P.O. Box 43305  Tucson, AZ  85733                |