diff options
author | Simon Marchi <simon.marchi@ericsson.com> | 2015-06-02 15:32:40 -0400 |
---|---|---|
committer | Simon Marchi <simon.marchi@ericsson.com> | 2015-06-02 15:32:57 -0400 |
commit | 3b462ec2bedca7392bf4720db44fdf2a46ad8b4d (patch) | |
tree | 00f38e40bcab9efa75a154ad7b8c3f57f2e8c407 /gdb/sparc64-linux-tdep.c | |
parent | 9c7fe3c5c2c9e4c3571c253cf77341e3f6adf94c (diff) | |
download | gdb-3b462ec2bedca7392bf4720db44fdf2a46ad8b4d.zip gdb-3b462ec2bedca7392bf4720db44fdf2a46ad8b4d.tar.gz gdb-3b462ec2bedca7392bf4720db44fdf2a46ad8b4d.tar.bz2 |
Fix =thread-exited not showing up when detaching (PR 15564)
I sent a patch in 2013 for this (incorrectly named =thread-created):
https://cygwin.com/ml/gdb-patches/2013-06/msg00129.html
Tom Tromey was ok with the change, but suggested to add a test as well.
Then I forgot about this patch until today. So here it is again, with the
corresponding test.
The problem is that the =thread-exited event does not appear when detaching
from a local process. It does appear with remote though. It's not a really
big deal, but I'd like it to be consistent.
Tested with local and remote Linux on my Ubuntu 14.04.
gdb/ChangeLog:
PR gdb/15564
* inferior.c (detach_inferior): Call exit_inferior_1 with silent = 0.
gdb/testsuite/ChangeLog:
PR gdb/15564
* gdb.mi/mi-detach.exp: New file.
Diffstat (limited to 'gdb/sparc64-linux-tdep.c')
0 files changed, 0 insertions, 0 deletions