[PATCH 0/2] Include count of unexpected core files in gdb.sum summary

[Pedro Alves <pedro@palves.net>]

It can happen that GDB, GDBserver, etc. even crashes _after_ gdb_exit,
during teardown, and thus such a crash won't be noticed by looking at
the gdb.sum file at all.  This series aims at improving that, by
including a new "unexpected core files" line in the gdb.sum summary.

For example, here's what I get on x86-64 Ubuntu 20.04, with this
series:

		 === gdb Summary ===

 # of unexpected core files      12          << new info
 # of expected passes            107557
 # of unexpected failures        35
 # of expected failures          77
 # of unknown successes          2
 # of known failures             114
 # of untested testcases         31
 # of unsupported tests          139

That is done by patch #2.

Patch #1 fixes some testcases to make sure they dump their cores under
their output dir instead of in build/gdb/testsuite/, as those cores
are not unexpected cores, and makes the testcases be able to find
their kernel-generated cores when the core file names aren't exactly
"gdb" or "gdb.PID".

Pedro Alves (2):
  Improve core file path detection & put cores in output dir
  Include count of unexpected core files in gdb.sum summary

 gdb/testsuite/Makefile.in                   |  9 ++-
 gdb/testsuite/gdb.base/annota1.exp          | 18 ++---
 gdb/testsuite/gdb.base/annota3.exp          | 18 ++---
 gdb/testsuite/gdb.base/bigcore.exp          | 38 ++-------
 gdb/testsuite/gdb.base/exitsignal.exp       | 11 ++-
 gdb/testsuite/lib/dg-add-core-file-count.sh | 40 ++++++++++
 gdb/testsuite/lib/gdb.exp                   | 86 ++++++++++++++++++++-
 7 files changed, 165 insertions(+), 55 deletions(-)
 create mode 100755 gdb/testsuite/lib/dg-add-core-file-count.sh


base-commit: c86acd3f180419c3d9825170492363fe2322fa8d
-- 
2.36.0