On Mar 14, 2011, at 1:33 PM, Tom Tromey wrote: > These new tests require a very new gdb in order to fully pass. In > particular these tests pointed out some buglets that are only fixed in > CVS, not in any release. > > > Trying to dynamically adjust the tests for the gdb version looks like a > pain. > > Maybe I could change the tests to check the gdb version and xfail the > tests for gdb < 7.3. Would that be ok?
Almost sounds more like unsupported. I'd just have a dynamic gdb check that tests a single feature and then gate all the others on it. If you test one of the last features to go in, you can then have them all turn off for the released gdbs, and when the new gdb is released, then they all just pop on. For hard core developers (those that have gdb trunk installed and do gcc trunk development) , they all pop on when they do an update/update install. Also, this is better than merely checking gdb versions, as someone could add support for the printers to their version of gdb (or gdb clone), and all the testcases would pop on, once they get the first one working. That said, the above is just a comment.
