Mail Archives: djgpp/1999/10/14/22:00:41
From: | "Johnny Chan" <jchan AT paclink DOT net>
|
To: | <djgpp AT delorie DOT com>
|
Subject: | RE: Q: Want to know the starting address and size of my program
|
Date: | Thu, 14 Oct 1999 17:58:41 -0700
|
Message-ID: | <000301bf16a8$6c6a8420$ae3d7a86@phoenix.com>
|
MIME-Version: | 1.0
|
X-Priority: | 3 (Normal)
|
X-MSMail-Priority: | Normal
|
X-Mailer: | Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
|
Importance: | Normal
|
In-Reply-To: | <E1FF8239A075D311AF7200A0C9D60AE30F9C70@probe-2.acclaim-euro.net>
|
X-MimeOLE: | Produced By Microsoft MimeOLE V5.00.2615.200
|
Reply-To: | djgpp AT delorie DOT com
|
X-Mailing-List: | djgpp AT delorie DOT com
|
X-Unsubscribes-To: | listserv AT delorie DOT com
|
good suggestion, Shawn,
>>But there is another option, if you make the memory test be
>>non-destructive. You can test a location by reading the old
>>value, changing the value, reading it back to make sure that
>>it truly did change, and then writing the original value back
>>when you are done, and in this case, as long as you don't
>>touch the specific few instructions that are making these
That's exactly what I have in mind. However, I still
have a hard time to figure out the location of that "critical"
code/data. I will try Eli's suggestion tonight.
>>checks (which can be just a small asm function that you have
>>direct control over), it doesn't matter if you stomp all over
>>the rest of your program. As long as you disable interrupts
Any DJGPP function to disable the interrupt?
>>and aren't running under any fancy OS, it should be pretty
>>safe to access whatever memory you like in this way.
--jC
- Raw text -