From: Kbwms AT aol DOT com
Message-ID: <5353477a.361bfe6b@aol.com>
Date: Wed, 7 Oct 1998 19:51:07 EDT
To: Ilya Ryzhenkov <orangy AT inetlab DOT com>
Cc: djgpp-workers AT delorie DOT com
Mime-Version: 1.0
Subject: Re: DLM v2.0 soon! ;))
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
X-Mailer: AOL 3.0 16-bit for Windows sub 38
Reply-To: djgpp-workers AT delorie DOT com

Subj:	 DLM v2.0 soon! ;))
To:	

Dear Ilya Ryzhenkov,

On 10-07-98 at 18:23:31 EST you wrote:
>
> Hello!
>
> Just wanted to drop a letter that I finally managed to deal
> with exceptions (and 387 emulation also) in my DLM library.
> It works fine with djgpp v2.02 & gcc 2.8.1, but ...
> Is there any _simple_ (i.e without rewriting libgcc parts)
> way to redefine standard behavior on unhandled exception ?
> It now just calls abort, which raises SIGABRT in turn and thus
> filling screen with uninformative text, far from real reason
> of halt.
>
> Comments ?

I suggest that you start by reading the November issue of C/C++
Users Journal, page 91.  The Questions and Answers column by
Pete Becker deals with such a problem and proposes a solution.


K.B. Williams