Extra diagnostic for tests

Vladimir Prus ghost@cs.msu.su
Sat Sep 16 11:19:00 GMT 2006


Vladimir Prus wrote:

> 
> Hi,
> at the moment, the dejagnu tests use PATH to find the gdb binary, and
> don't report which gdb binary is used. As result, when running runtest
> manually on one test, one can test with different gdb from the one used by
> 'make check'.
> 
> The attached patch makes gdb print to log file the location of gdb, and
> also makes sure invocation parameters are always printed to log file.
> While we're on it, the 'serialport' parameter to 'target' command is also
> reported.

So, what's opinion on this patch, after all?

I think the part about better reporting 'target remote' seen no objections,
OK to commit that?

Speaking of gdb PATH, I've noticed that the very last line of dejagnu output
contains the full path to gdb -- apparently I used 'Ctrl-C' too much.

Anyway, I think getting this information into log file is still desirable,
and it makes sure that .log file is sufficient to reproduce a test
failures -- console output might be no longer handy.

- Volodya





More information about the Gdb-patches mailing list