Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site ttrdc.UUCP Path: utzoo!watmath!clyde!cbosgd!ihnp4!ltuxa!ttrdc!levy From: levy@ttrdc.UUCP (Daniel R. Levy) Newsgroups: net.lang.c,net.unix-wizards,net.arch Subject: Re: (3b2) functions in data space Message-ID: <803@ttrdc.UUCP> Date: Tue, 18-Mar-86 04:20:24 EST Article-I.D.: ttrdc.803 Posted: Tue Mar 18 04:20:24 1986 Date-Received: Wed, 19-Mar-86 05:13:18 EST References: <728@petsd.UUCP> <1486@devwrl.DEC.COM> <622@bentley.UUCP> <802@ttrdc.UUCP> Organization: AT&T, Computer Systems Division, Skokie, IL Lines: 25 Xref: watmath net.lang.c:8185 net.unix-wizards:17261 net.arch:2856 Small addendum to my previous posting: I must give credit to Ehud Reiter (harvard!reiter) for the idea on how to do this (he answered my question as to how it was accomplished in Fortran, and I tried it in both f77 and C, and it worked). I am sure that I am indeed running the data space rather than just capturing a pointer to the text space, since in another version of the test program I did a dump of the buffer, which compared identically to a dis(1) disas- sembly of the LINKED executable section that I copied. Maybe it would be a good idea to have a "dummy function" which would be copied into an array then modified as needed, to avoid the nitty gritty problems of the final linking? (I noticed that a disassembly of the object [.o] file was a little different than the linked version, having places where ld(1) evidently must "fill in the blanks" to have a valid sequence of code when all external symbols are resolved.) -- ------------------------------- Disclaimer: The views contained herein are | dan levy | yvel nad | my own and are not at all those of my em- | an engihacker @ | ployer or the administrator of any computer | at&t computer systems division | upon which I may hack. | skokie, illinois | -------------------------------- Path: ..!{akgua,homxb,ihnp4,ltuxa,mvuxa, vax135}!ttrdc!levy