[review,gdb/testsuite] Fix UNRESOLVED in gdb.server/server-kill-python.exp

  Change URL: https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/760
......................................................................

[gdb/testsuite] Fix UNRESOLVED in gdb.server/server-kill-python.exp

The test-case gdb.server/server-kill-python.exp runs fine by itself:
...
Running src/gdb/testsuite/gdb.server/server-kill-python.exp ...

                === gdb Summary ===

nr of expected passes            3
...

But if we run f.i. gdb.server/file-transfer.exp before it, we get instead:
...
Running src/gdb/testsuite/gdb.server/server-kill-python.exp ...
ERROR: GDB process no longer exists

                === gdb Summary ===

nr of expected passes            13
nr of unresolved testcases       1
...

We can see the origin of the problem here:
...
spawn gdbserver --once localhost:2347 \
  build/gdb/testsuite/outputs/gdb.server/file-transfer/file-transfer \
  build/gdb/testsuite/outputs/gdb.server/server-kill-python/server-kill-python^M
Process build/gdb/testsuite/outputs/gdb.server/file-transfer/file-transfer
  \ created; pid = 9464^M
Listening on port 2347^M
...

The spawn of the gdbserver for the server-kill-python test-case gets as
executable argument the file-transfer binary.

This is caused by proc gdbserver_spawn attempting to load the exec file in
$file_last_loaded.  This is something that is meant to load the same exec in
the gdbserver that was earlier loaded into gdb.

In this test-case however, nothing has been loaded into gdb by the test-case,
and consequently we load the file that was loaded into gdb in the previous
test-case.

Fix this by unsetting $file_last_loaded before spawning gdbserver.

Build and reg-tested on x86_64-linux.

gdb/testsuite/ChangeLog:

2020-01-31  Tom de Vries  <tdevries@suse.de>

	PR testsuite/25488
	* gdb.server/server-kill-python.exp: Unset $file_last_loaded before
	spawning gdbserver.

Change-Id: Ic385e08cbd34cbf85518720cf5695b4ff6619f4b
---
M gdb/testsuite/gdb.server/server-kill-python.exp
1 file changed, 3 insertions(+), 0 deletions(-)
  

Simon Marchi has posted comments on this change.

Change URL: https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/760
......................................................................


Patch Set 1:

Commit b1b53fb3ef077bf4412da53f0057b9c0e9ed4f3e added the same fix to gdb.server/solib-list.exp.  What would you think of unsetting last_loaded_file in gdb_init?  This is ran at the beginning of each test case, so I think it would be a better long-term fix, rather than patching each test case.
  

Andrew Burgess has posted comments on this change.

Change URL: https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/760
......................................................................


Patch Set 1:

> Patch Set 1:
> 
> Commit b1b53fb3ef077bf4412da53f0057b9c0e9ed4f3e added the same fix to gdb.server/solib-list.exp.  What would you think of unsetting last_loaded_file in gdb_init?  This is ran at the beginning of each test case, so I think it would be a better long-term fix, rather than patching each test case.

This sounds like a good idea to me.
  

Tom de Vries has posted comments on this change.

Change URL: https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/760
......................................................................


Patch Set 1:

> Patch Set 1:
> 
> > Patch Set 1:
> > 
> > Commit b1b53fb3ef077bf4412da53f0057b9c0e9ed4f3e added the same fix to gdb.server/solib-list.exp.  What would you think of unsetting last_loaded_file in gdb_init?  This is ran at the beginning of each test case, so I think it would be a better long-term fix, rather than patching each test case.
> 
> This sounds like a good idea to me.

Ack, that works, I'll test and resubmit.
  

Tom de Vries has abandoned this change. ( https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/760 )

Change subject: [gdb/testsuite] Fix UNRESOLVED in gdb.server/server-kill-python.exp
......................................................................


Abandoned

Resumitted at https://sourceware.org/ml/gdb-patches/2020-02/msg00279.html