Mail Archives: djgpp/1999/10/12/18:54:41
Eli,
>>-----Original Message-----
>>Please define ``starting address'' and ``size''.
>>A program consists of several sections:
>>there's code, there's data, there's the
>>heap, and a few others.
>>What exactly do you want to know, and for what purpose?
Actually, I am trying to do a FULL system memory scan and
read/write test. I want to know where the code starts and where
the data stays so that I can add some protection based on these
information and my program will not over write any code or
data or heap or others accidentially.
>>If you want to reach the loader from within a running DJGPP
>>program, then you can't: its space is reused for the transfer
>>buffer, after the loader has done its job.
What will happen if my program does some memory read/write test
on the memory area where is the loader located originally?
>>You can read this memory with dosmemget, but since it is used for the
>>transfer buffer, you will get garbage: the startup code
>>begins using the transfer buffer quite early, so by the time you get
>>there, it's overwritten many times.
>>Nothing will happen. But why do you need something like that?
>>It might help if you explain some more. The above sounds as
>>if you have already settled on some solution(s) to your problems,
>>but you based the solution on incorrect assumptions.
>>It might be a good idea to post a description of your original
>>problems. Then someone might come up with ideas about how to
>>solve them.
- Raw text -