Date: Sun, 25 Oct 1998 20:09:39 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Roland Schulz <Schulz AT gmx DOT net>
cc: djgpp AT delorie DOT com
Subject: Re: Debugging problems with dj 2.01
In-Reply-To: <3632FEB7.87CF726E@gmx.net>
Message-ID: <Pine.SUN.3.91.981025200917.24396X-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com


On Sun, 25 Oct 1998, Roland Schulz wrote:

> when I ran the program with
> the error under Rhide, it didn't produce any error at all. Is there any
> way to tell Rhide not to ignore those exeptions?

It doesn't ignore them.  But sometimes programs don't trigger
exceptions when they run under a debugger.

> Next I tried to view the crash dump by redirecting the standard error
> using redir, since I couldn't read it, because the crash happened in
> graphic mode (using grx23). But the name of the crashed program in that
> crash dump wasn't my program name but redir.

The current version of redir doesn't live well with crashed programs,
because it doesn't mask exceptions before running the subsidiary
program.  So when the subsidiary program crashes, redir can crash as
well.

This is corected in v2.02, but until that version is out, you could
try the SCRIPT program (the URL is in the FAQ, section 6.14), or the
PrintScreen key.