Date: Sun, 9 Aug 1998 13:10:49 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: George Foot <george DOT foot AT merton DOT oxford DOT ac DOT uk>
cc: djgpp AT delorie DOT com
Subject: Re: help! SIGILL?!?
In-Reply-To: <199808062307.AAA13027@sable.ox.ac.uk>
Message-ID: <Pine.SUN.3.91.980809130245.28598A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Fri, 7 Aug 1998, George Foot wrote:

> I think someone once said that it would be complicated, because of the 
> way the program's memory is divided into separate blocks.

That was me ;-).  But it seems that debugging core files doesn't really
require to reconstruct the memory layout.  This layout is important if 
the debuggee could call `sbrk'.  Since it cannot do that in post-mortem
debugging, all you need to care about is that you can find a variable or
an instruction given their address.

> The impression I got was that GDB likes to load the core as 
> a single continuous block, in which case we might get very large core 
> files if the program's DPMI memory blocks aren't tightly packed.

Even if this is true, it just means that a program which wants to support 
core dumps needs to be built with unixy sbrk algorithm: not an impossible 
requirement IMHO.