This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [rfa/testsuite] test script for pr gdb/1056, divide by zero ingdb


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



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]