Andrew Cagney wrote:
Fernando,
What is the resolution of this thread?
http://sources.redhat.com/ml/gdb-patches/2002-10/msg00508.html
(you'll probably want to read all of it :-)
(I'm now going back and emptying my mail box :-()
Andrew
Hi Andrew,
I am just starting to think about this, so bear with me while I think aloud a little bit :-) There are lots of good points made on that discussion and I don't think this is a clear cut yet or no, lets vote, or anything like that. I am trying to see if I can collect all good suggestions and propose a course of action.
It seems that a widespread concern is not to through the baby with the water. On the other hand there is the feeling that we do not act now nothing will ever happen. And we all agree that many xfails were added incorrectly.
Independently of the "big plan", one thing is clear. If you know that a xfail is incorrect (I mean, know for good), then it should be ripped off. But read on...
Maybe we may not be in full agreement here, but I think it would be nice to enter a bug report even if does not include a full analysis -- that should come eventually. Something like "something is wrong with the '--xxx-yyy' command output" may eventually cause someone to look into it. And you can make the xfail a kfail in that case, which is much better. But I know it is much more work than just removing the xfail and letting the test fail -- you would have to enter 28 bug reports just for the MI tests. Still sounds like a better approach to me, but there is no consensus on it.
Some things I think worth noting.