Date:	Sun, 14 Mar 1999 11:04:17 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Nate Eldredge <nate AT cartsys DOT com>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: Debugger problem
In-Reply-To:	<36E9C233.22CE67A0@cartsys.com>
Message-ID:	<Pine.SUN.3.91.990314110358.18100S-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Fri, 12 Mar 1999, Nate Eldredge wrote:

> If GDB
> tries to access a page I have uncommitted, GDB itself crashes.  "Cannot
> continue from exception..."

What did you expect?  After all, GDB runs in the same process as the
debuggee, right?

> I'm not sure if there is anything to be done about this, but if so it's
> going to make my system rather a pain to use.

Can't you fix the problem (by committing the page) before returning?
The ``cannot continue'' problem is easy to work around (just longjmp
instead of returning), but you need to fix the cause of the exception
first.

I'm afraid I don't have a clear idea of what you wanted to do,
though.  Suppose the debugger weren't crashing: what did you want to
do then?  Why did you try to access the uncommitted page in the first
place?

- Raw text -