[Bug mi/15564] MI thread-exited event inconsistency when detaching

["cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=15564

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Simon Marchi <simark@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=3b462ec2bedca7392bf4720db44fdf2a46ad8b4d

commit 3b462ec2bedca7392bf4720db44fdf2a46ad8b4d
Author: Simon Marchi <simon.marchi@ericsson.com>
Date:   Tue Jun 2 15:32:40 2015 -0400

    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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.