From: Martin Str|mberg <ams AT ludd DOT luth DOT se>
Message-Id: <200101211831.TAA10623@father.ludd.luth.se>
Subject: Re: Debugging on 386
In-Reply-To: <7263-Sun21Jan2001185503+0200-eliz@is.elta.co.il> from Eli Zaretskii at "Jan 21, 2001 06:55:03 pm"
To: djgpp-workers AT delorie DOT com
Date: Sun, 21 Jan 2001 19:31:42 +0100 (MET)
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
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
Precedence: bulk

According to Eli Zaretskii:
> > From: Martin Str|mberg <ams AT ludd DOT luth DOT se>
> > Date: Sun, 21 Jan 2001 17:06:34 +0100 (MET)
> > 
> > According to Martin Str|mberg:
> > > According to Eli Zaretskii:
> > > > Try "handle SIGEMT nostop noprint".
> > > 
> > > Ok, now I get an endless loop of:
> > > 
> > > Coprocessor Error at eip=00009616, x87 status=Exiting due to signal SIGFPE
> > 
> > A restart and recompilation later, I can't repoduce this.
> 
> What exactly is not reproducible?  Do you mean to say that with SIGEMT
> set to noprint nostop the program now runs as you'd expect?  Or do you
> mean to say that even the original report of SIGEMTs being triggered
> cannot be reproduced now?

No, the endless loop of "Coprocessor Error at eip=00009616, x87
status=Exiting due to signal SIGFPE" isn't reproducible.

The SIGEMT and SIGFPE still occur.


Right,

						MartinS