This is the mail archive of the
mailing list for the GDB project.
GDB `cannotfix' pr state, require PR with xfail `moving forward'.
- From: Andrew Cagney <ac131313 at redhat dot com>
- To: gdb at sources dot redhat dot com
- Date: Thu, 16 Jan 2003 14:35:15 -0500
- Subject: GDB `cannotfix' pr state, require PR with xfail `moving forward'.
There is currently a long thread (Remove all setup_xfail...)'s on
gdb-patches@. Several proposals, I think, can already be identified at
this point in the discussion.
- yank the existing xfail PR markings (but not the actual xfails) (they
apply to old internal Red Hat and HP bug databases and hence are
- `moving forward' all new xfails, and all modifications to existing
xfail's should include a bug report (this way, new analyzed vs old
unanalized xfail's can easily be differentiated).
- GDB have a new closed state `cannotfix'; or a new class `xfail' or
`notabug' or ...; or even reuse the class `mistaken' that can be used to
categorize xfail bug reports (not sure which is better here).
PS: The state `willnotfix' was suggested. I think that is wrong. GDB
shouldn't refuse to fix a real problem (just drop the priority to low),
and here the problem is one of cannot fix.