diff options
author | Don Breazeal <donb@codesourcery.com> | 2015-05-28 14:26:03 -0700 |
---|---|---|
committer | Don Breazeal <donb@codesourcery.com> | 2015-05-28 14:37:56 -0700 |
commit | 8dd06f7a89b6eb7b646349f50746b3d2e85ed5de (patch) | |
tree | d58780dccd9e542936efeac34574dead7dec9ca7 /gdb/python/py-event.c | |
parent | a051152b640c8bd1286ae71410f0b861ee158691 (diff) | |
download | gdb-8dd06f7a89b6eb7b646349f50746b3d2e85ed5de.zip gdb-8dd06f7a89b6eb7b646349f50746b3d2e85ed5de.tar.gz gdb-8dd06f7a89b6eb7b646349f50746b3d2e85ed5de.tar.bz2 |
Make remote follow fork 'Detaching' message match native
This patch fixes a couple of failures in gdb.base/foll-vfork.exp for
extended-remote targets. The failures were the result of the
verbose/debug "Detaching..." messages in infrun.c:follow_fork_inferior
not matching what was expected in the extended-remote case.
The path modifies the ptids used in the messages to ensure that they
print "process nnn" instead of (possibly) "Thread nnn.nnn". The
detach is a process-wide operation, so we need to use a process-
style ptid regardless of what type of ptid target_pid_to_str returns.
Tested on x86_64 GNU/Linux, native, remote, extended-remote.
gdb/
* infrun.c (follow_fork_inferior): Ensure the use of
process-style ptids (pid,0,0) in verbose/debug "Detaching"
messages.
Diffstat (limited to 'gdb/python/py-event.c')
0 files changed, 0 insertions, 0 deletions