delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/2001/01/21/11:59:31

Date: Sun, 21 Jan 2001 18:55:03 +0200
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: Martin Str|mberg <ams AT ludd DOT luth DOT se>
Message-Id: <7263-Sun21Jan2001185503+0200-eliz@is.elta.co.il>
X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.6
CC: djgpp-workers AT delorie DOT com
In-reply-to: <200101211606.RAA10132@father.ludd.luth.se> (message from Martin
Str|mberg on Sun, 21 Jan 2001 17:06:34 +0100 (MET))
Subject: Re: Debugging on 386
References: <200101211606 DOT RAA10132 AT father DOT ludd DOT luth DOT se>
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

> 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?

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019