From: broeker AT acp3bf DOT knirsch DOT de (Hans-Bernhard Broeker)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Q: Want to know the starting address and size of my program
Date: 18 Oct 1999 15:50:55 +0200
Organization: RWTH Aachen, III. physikalisches Institut B
Message-ID: <7uf8k0$apn@acp3bf.knirsch.de>
References: <001401bf15b7$9a7635e0$ae3d7a86 AT phoenix DOT com>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 940254659 14416 137.226.32.75 (18 Oct 1999 13:50:59 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 18 Oct 1999 13:50:59 GMT
X-Newsreader: TIN [version 1.2 PL2]
Lines: 21
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Johnny Chan (jchan AT paclink DOT net) wrote:

> Is it possible to find out exactly where is my data, stack, code area
> located. Some of the routine will test the RAM bit by bit. The code
> and data will be very small, no heap will be involved here.
> I am trying to maximize the test coverage and limited the untouched 
> area that code and data area. The stub program should know exactly
> where is this "program" located. Is there any way to collect this
> piece of information?

There's only *one* method to scan really all of the memory, and you
can't use that from any program started under control of an operating
system. You have to do it the way memtest86 does it: create a bootable
program image (no OS or anything involved, just the BIOS reading your
image and booting it), put it onto a floppy and boot from that.  In
addition, the program has to make a copy of itself in another
location, so it can reliably test the memory the program itself is
located in.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.