Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!usc!apple!agate!volcano.Berkeley.EDU!kawakami
From: kawakami@volcano.Berkeley.EDU (John Kawakami)
Newsgroups: comp.sys.atari.st.tech
Subject: Re: Location of variables in executable files.
Message-ID: <1990Nov16.073620.8796@agate.berkeley.edu>
Date: 16 Nov 90 07:36:20 GMT
References: <1990Nov11.013428.4566@cs.utk.edu> <2737@atari.UUCP> <1990Nov13.144721.21402@cs.utk.edu>
Sender: usenet@agate.berkeley.edu (USENET Administrator)
Reply-To: kawakami@volcano.Berkeley.EDU (John Kawakami)
Organization: ucb
Lines: 25

In article <1990Nov13.144721.21402@cs.utk.edu> andrew@cs.utk.edu (Andrew Krzywdzinski) writes:
>I was thinking (erroneously) that Getmpb would tell me where the program
>being executed starts in memory, so that I can match the location of
>the variable in the "self modifying" program and on the disk. Now that
>I've learned more about the format of the executable files, I know better.
>The suggestion I received was to look at the initialized data segment,
>and look for my magic number. This sounds like it might work, but seems
>like a bit of a hack.
>I suppose there is no better way of doing it, so I'll try it the hack-way.

Ok everyone, repeat after me:

All hail the Mac resource forks
All hail the Mac resource forks
All hail the Mac resource forks

Maybe this is the next thing Atari can standardize :-)  Now that the
PC+Windows has it (like outline fonts, graphics independence, etc.)

I guess that's the bummer part of having an Atari (or Amiga): even cool
system-safe addons have to be done in-house.

John Kawakami                  kawakami@ocf.berkeley.edu
                               ucbvax!ocf.berkeley.edu!kawakami
Amateur crank!                 My Atari Macks!