Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Mark Kettenis <kettenis@chello.nl>
Cc: ian@wasabisystems.com, mec.gnu@mindspring.com,
	david@streamline-computing.com, gdb-patches@sources.redhat.com
Subject: Re: [Patch] x % 0 hangs
Date: Mon, 28 Jun 2004 14:25:00 -0000	[thread overview]
Message-ID: <40E02A56.1040306@gnu.org> (raw)
In-Reply-To: <200406271715.i5RHFARS007952@elgar.kettenis.dyndns.org>

>    From: Ian Lance Taylor <ian@wasabisystems.com>
>    Date: 27 Jun 2004 11:06:19 -0400
> 
>    Andrew Cagney <cagney@gnu.org> writes:
> 
>    > > The only approach that's somewhat
>    > > portable is longjmp-ing out of the signal handler, and even that seems
>    > > to have its problems on some platforms.
>    > 
>    > I'm curious, which platforms?
> 
> Over the years I've seen quite a few bug-reports about this failing to
> work, but I can't remember exectly which platforms were affected.

We need start with a working assumption that GDB is being run on POSIX 
compliant systems and that implies a working sigsetjmp / siglongjmp. 
Only when someone comes forward with a problematic system should we 
worry about it (and possibly not even then).

(BTW, the other way to handle this is to implement a s/w emulation of 
the inferior's arithmetic, that would never throw a SIGFPE).

Andrew



  reply	other threads:[~2004-06-28 14:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-26 15:44 Michael Elizabeth Chastain
2004-06-26 22:52 ` Mark Kettenis
2004-06-26 23:19   ` Andrew Cagney
2004-06-27 15:06     ` Ian Lance Taylor
2004-06-27 17:15       ` Mark Kettenis
2004-06-28 14:25         ` Andrew Cagney [this message]
2004-06-29 23:35           ` Mark Kettenis
2004-07-17  2:43             ` Andrew Cagney
  -- strict thread matches above, loose matches on Subject: below --
2004-06-26  9:23 David Lecomber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40E02A56.1040306@gnu.org \
    --to=cagney@gnu.org \
    --cc=david@streamline-computing.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=ian@wasabisystems.com \
    --cc=kettenis@chello.nl \
    --cc=mec.gnu@mindspring.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox