From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28702 invoked by alias); 18 Oct 2003 17:01:25 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 28694 invoked from network); 18 Oct 2003 17:01:24 -0000 Received: from unknown (HELO concert.shout.net) (204.253.184.25) by sources.redhat.com with SMTP; 18 Oct 2003 17:01:24 -0000 Received: from duracef.shout.net (duracef.shout.net [204.253.184.12]) by concert.shout.net (8.12.10/8.12.10) with ESMTP id h9IH1NVg020736; Sat, 18 Oct 2003 12:01:23 -0500 Received: from duracef.shout.net (localhost [127.0.0.1]) by duracef.shout.net (8.12.10/8.12.9) with ESMTP id h9IH1Nfa020956; Sat, 18 Oct 2003 12:01:23 -0500 Received: (from mec@localhost) by duracef.shout.net (8.12.10/8.12.9/Submit) id h9IH1Ngb020955; Sat, 18 Oct 2003 13:01:23 -0400 Date: Sat, 18 Oct 2003 17:01:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200310181701.h9IH1Ngb020955@duracef.shout.net> To: brobecker@gnat.com Subject: Re: [rfa/testsuite] test script for pr gdb/1056, divide by zero in gdb Cc: gdb-patches@sources.redhat.com X-SW-Source: 2003-10/txt/msg00603.txt.bz2 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 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. Michael C