gdb testsuite results (many regressions)

I don't know if this is tracked anywhere or just a "patches" welcome issue... Anyway, if any of it is from bad DST it could impact lldb as well and why I'm sending this..

You say “regressions” in the topic - are they actually regressions? Did these pass at some point?

We track a modified version of the GDB 7.5 test suite as a Clang buildbot here: http://lab.llvm.org:8011/builders/clang-x86_64-ubuntu-gdb-75 (you can find the sources in the LLVM project ‘cte’). It contains some amount of XFAILs for variations between compilers or Clang bugs (that all have bugs in llvm.org/bugs filed).

I haven’t had a chance/taken the time to port these xfails and test changes to upstream GDB, but that’d be a nice thing to do at some point and then setup a bot that is ToT GDB and ToT Clang so we can find bugs in either (since so much of the debug info experience is an implicit contract between producer and consumer - so end to end testing is a necessary evil)

I found
https://github.com/llvm-mirror/clang-tools-extra

, but at a glance I don't see anything which appears to be a modified gdb testsuite. Sorry - can you point me at the svn or git sources.

Thanks

It is this one:
http://llvm.org/svn/llvm-project/clang-tests-external/trunk/

Thanks - Current gdb is 7.6.1 and what's the plan for the future of maintaining this? Did upstream reject the patches? Hopefully they are friendly to such things...

It is this one:
http://llvm.org/svn/llvm-project/clang-tests-external/trunk/

That would be the one, yes. Sorry for the confusion, I just have it aliased
to 'cte' which is, as you found, ambiguous with 'clang-tools-external'.

Thanks - Current gdb is 7.6.1 and what's the plan for the future of

maintaining this?

For the moment there's no particular plan other than to use what's already
there as a regression suite.

Did upstream reject the patches?

I haven't attempted to upstream much of any of this - I upstreamed some
bugfixes to the test running scripts, but haven't found the time/urgency to
upstream the actual XFAILs, test changes, etc, and setup a ToT GDB/Clang
bot.

Hopefully they are friendly to such things...

Probably. I just haven't asked - anyone is welcome to, it's just not a
priority for me right now. The changes I've made to the 7.5 suite in
clang-tests-external should be fairly targeted and easy to find via
revision history and/or diffing compared to the initial commit. If anyone
wants to take those and upstream them to GDB root, that'd be great.

- David

It is this one:
http://llvm.org/svn/llvm-project/clang-tests-external/trunk/

That would be the one, yes. Sorry for the confusion, I just have it
aliased to 'cte' which is, as you found, ambiguous with
'clang-tools-external'.

Thanks - Current gdb is 7.6.1 and what's the plan for the future of

maintaining this?

For the moment there's no particular plan other than to use what's already
there as a regression suite.

To elaborate on this there's very few differences with current gdb and the
gdb 7.5 in the testsuite for those failures and the failures we've looked
at.

-eric