Message-Id: <3.0.1.32.20010424150443.006968bc@wingate>
X-Sender: n_abing#ns DOT roxas-online DOT net DOT ph AT wingate
X-Mailer: Windows Eudora Pro Version 3.0.1 (32)
Date: Tue, 24 Apr 2001 15:04:43 +0800
To: djgpp-workers AT delorie DOT com
From: "Nimrod A. Abing" <n_abing AT ns DOT roxas-online DOT net DOT ph>
Subject: Re: Fixed core dumper in dpmiexcp.c
Cc: eliz AT is DOT elta DOT co DOT il, broeker AT physik DOT rwth-aachen DOT de
In-Reply-To: <Pine.SUN.3.91.1010423135524.25673U-100000@is>
References: <3 DOT 0 DOT 1 DOT 32 DOT 20010423075611 DOT 006cf688 AT wingate>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

Hello.

At 01:55 PM 04/23/2001 +0300, you wrote:
>> Eli, is it possible for the __djgpp_memory_handle_list to
>> become corrupt prior to an exception?
>
>A bug can do that.  Otheriwse, __djgpp_memory_handle_list should be
>right at all times, since nohing will work if it isn't.  An exception
>might invalidate some of the registers, but it does nothing to the
>variables which live inside an application, nor to its page tables.

What kind of bug? Would programs that leak memory also cause this to happen
somehow?

nimrod_a_abing
--------------

+========================================+
|  Home page: www.geocities.com/n_abing  |
+========================================+

"Tinimbang ka ngunit kulang."
If you understand that phrase, i-email mo'ko. ;-)