[binutils-gdb] gdbserver: move_out_of_jump_pad_callback misses switching current thread

[sergiodj+buildbot at redhat dot com]

*** TEST RESULTS FOR COMMIT f0ce0d3a331129309a46a6a9ac85fce35acae72b ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: f0ce0d3a331129309a46a6a9ac85fce35acae72b

gdbserver: move_out_of_jump_pad_callback misses switching current thread
While hacking on the fix for PR threads/18600 (Threads left stopped
after fork+thread spawn), I once saw its test (fork-plus-threads.exp)
FAIL against gdbserver because move_out_of_jump_pad_callback has a
gdb_breakpoint_here call, and the caller isn't making sure the current
thread points to the right thread.  In the case I saw, the current
thread pointed to the wrong process, so gdb_breakpoint_here returned
the wrong answer.  Unfortunately I didn't save logs.  Still, seems
obvious enough and it should fix a potential occasional racy FAIL.

Tested on x86_64 Fedora 20.

gdb/gdbserver/ChangeLog:
2015-08-06  Pedro Alves  <palves@redhat.com>

	* linux-low.c (move_out_of_jump_pad_callback): Temporarily switch
	the current thread.