Date:	Thu, 29 Mar 2001 11:11:37 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	"Nimrod A. Abing" <n_abing AT ns DOT roxas-online DOT net DOT ph>
cc:	Charles Sandmann <sandmann AT clio DOT rice DOT edu>, djgpp-workers AT delorie DOT com
Subject:	Re: dpmiexcp.c with core dumping
In-Reply-To:	<3.0.1.32.20010329134717.006b3a78@wingate>
Message-ID:	<Pine.SUN.3.91.1010329110847.3269E-100000@is>
MIME-Version:	1.0
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

On Thu, 29 Mar 2001, Nimrod A. Abing wrote:

> >I would also like to see a "standard" format, but there is a problem
> >when we use the non-move sbrk().  Since Windows just loves returning 
> >non-contiguous memory blocks all over the place (sometimes below the
> >base address, which makes it look like a 4Gb address space) the core
> >files are huge unless they are dumped in pieces.  This also makes it
> >a real pain to process the core files also...
> 
> That explains why SIGSEGVs occured when dumping core from a program running
> in a Win9x DOS box.

It does?  I don't see how: the code seems to walk the DPMI memory handles 
that are created by sbrk when it allocates memory from the DPMI host.  So 
the pages recorded in the handles should be mapped into our process, and 
Page Faults shouldn't happen, I think.  Am I missing something?

> As for this "standard" format for core files, does anyone know where I can
> find any docs for this? Even murky ones will do :-)

I will ask for help on the GDB mailing list.

> One issue has been bothering me lately though, what about memory paged to
> disk?

What about it?  The DPMI host should page it in when you reference 
it---that's what VM is all about ;-)

- Raw text -