Extra diagnostic for tests

[Vladimir Prus]

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.

OK?

- Volodya

2006-09-13  Vladimir Prus  <vladimir@codesourcery.com>

	* lib/gdb.exp (default_gdb_start): Always add
	invocation command to log file. Report the location where
	gdb was found.

	* lib/gdbserver-support.exp (gdb_target_cmd): Report
	the serialport on connection, not just target kind.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gdb_testing_diagnostics.diff
Type: text/x-diff
Size: 1876 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/gdb-patches/attachments/20060913/201365c2/attachment.bin>