From: Andrew Cagney <cagney@gnu.org>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: brobecker@gnat.com, gdb-patches@sources.redhat.com
Subject: Re: [rfa/testsuite] test script for pr gdb/1056, divide by zero in gdb
Date: Tue, 21 Oct 2003 00:04:00 -0000 [thread overview]
Message-ID: <3F947811.6030805@gnu.org> (raw)
In-Reply-To: <200310181701.h9IH1Ngb020955@duracef.shout.net>
> Joel asks:
>
>> What is our policy regarding the insertion of URLs pointing to GDB PRs,
>> or URLs in general? I would prefer that we actually copy the relevant
>> information from the URL rather than inserting the URL.
>
>
> I'm not aware of an actual policy about this.
I'm not either.
While ".../gdb/bugs/<PR>" will out last any switch to mozilla (re-number
over my dead body :-), I don't think people will appreciate having
"redhat" embedded in the file.
I'd just stick to quoting the GDB pr number and any relevant text.
> I like the URL because the PR database is the central repository
> for information about bugs in gdb. It's easy for anyone to add new
> information to the PR database, but it requires an FSF copyright
> assignment and maintainer approval to add information to a test case.
>
> I think that this test case has enough information even if
> the PR database disappears. Specifically:
>
> # When SIGFPE happens, the operating system may restart the
> # offending instruction after the signal handler returns,
> # rather than proceeding to the next instruction. This happens
> # on i686-pc-linux-gnu with a linux kernel. If gdb has a naive
> # signal handler that just returns, then it will restart the
> # broken instruction and gdb gets an endless stream of SIGFPE's
> # and makes no progress.
>
> If you want even more text in the test case, I'm open to patches.
Anyway, yes ok.
Andrew
next prev parent reply other threads:[~2003-10-21 0:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-18 17:01 Michael Elizabeth Chastain
2003-10-21 0:04 ` Andrew Cagney [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-21 0:32 Michael Elizabeth Chastain
2003-10-18 15:25 Michael Elizabeth Chastain
2003-10-18 16:41 ` Joel Brobecker
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=3F947811.6030805@gnu.org \
--to=cagney@gnu.org \
--cc=brobecker@gnat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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