Re: gdb.gdb/ testcase issues.

[Michael Chastain <mec dot gnu at mindspring dot com>]

Manoj Iyer <manjo@austin.ibm.com> wrote:
> Will get back to you on that.

Okay.  I can't accept any patches larger than trivial without
a copyright assignment, though.

> The reason is, the GDB that is shipped in a distro is stripped, and I used
> the --tool_exec= option to use this GDB that is installed in /usr/bin.

Ah, that is a valid use case for testing a stripped gdb.

First it would help to file a PR to track this issue.

It would be nice to have some common code for this.

Three of the four test scripts in gdb.gdb have their own 'setup_test',
and the fourth script has another copy of the same code.  I would like
to see the common code factored into one place, lib/self-support.exp.

Then setup_test calls gdb_load which calls gdb_file_cmd.  You could get
into gdb_file_cmd and detect "(no debugging symbols found)" and add a
channel to return that information.  Or, in setup_test, you could
do something right after the call to gdb_load to check for debugging
symbols.

If there are no debugging symbols, then I think that the test script
should return one UNRESOLVED result and not continue testing.

I'm not sure UNRESOLVED is the right result.  Perhaps UNTESTED would
be better.  But not UNSUPPORTED -- UNSUPPORTED means that a feature
is missing in the system under test.

Michael