home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.aix
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!mips!darwin.sura.net!zaphod.mps.ohio-state.edu!malgudi.oar.net!news.ans.net!newsgate.watson.ibm.com!yktnews!admin!minnie!gerth
- From: gerth@watson.ibm.com (John Gerth)
- Subject: Re: Help with nlist(), XCOFF, and memory architecture...
- Sender: news@watson.ibm.com (NNTP News Poster)
- Message-ID: <1992Aug20.012457.5537@watson.ibm.com>
- Date: Thu, 20 Aug 1992 01:24:57 GMT
- Disclaimer: This posting represents the poster's views, not necessarily those of IBM
- References: <PAVEL.92Aug15180402@pixel.SLAC.Stanford.EDU> <PAVEL.92Aug19163010@pixel.SLAC.Stanford.EDU>
- Nntp-Posting-Host: minnie.watson.ibm.com
- Organization: IBM T.J. Watson Research Center
- Lines: 20
-
- The call ld_getinfo() in <sys/ldr.h> is documented as something for
- the kernel only and so there isn't any mention of it elsewhere.
- It's moral equivalent for us mere mortals is loadquery() with the
- L_GETINFO request -- which is documented (and points to <sys/ldr.h>).
-
- I'm pretty sure that the TOC and the 3-word function descriptor
- is documented in the Assembler Language manual, along with all
- the linkage conventions and whatnot. The philosophical and design
- rationales for the TOC are argued by the AIX architects in
- "RISC System/6000 Technology" (order SA23-2619) in an article
- on dynamic loading.
-
- The foregoing notwithstanding, I do believe that this stuff is not
- adequately explained or cross-referenced. Fundamental system services
- like the binder and program contents management must be comprehensively
- documented to encourage responsible use and exploitation of their
- capabilities. In these matters, ignorance is not bliss.
-
- --
- John Gerth gerth@watson.ibm.com (914) 784-7639
-