This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug server/20627] GDBserver can not be closed


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

--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Yao Qi <qiyao@sourceware.org>:

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

commit 17e16485989c7e91ba1ec5abf397f7f91a299eec
Author: Yao Qi <yao.qi@linaro.org>
Date:   Fri Sep 30 18:39:12 2016 +0100

    PR 20627: Use resume_stop to stop lwp

    Commit 049a8570 (Use target_continue{,_no_signal} instead of target_resume)
    replaces the code stopping lwp with target_continue_no_signal in
    target_stop_and_wait, like this,

    -  resume_info.thread = ptid;
    -  resume_info.kind = resume_stop;
    -  resume_info.sig = GDB_SIGNAL_0;
    -  (*the_target->resume) (&resume_info, 1);
    +  target_continue_no_signal (ptid);

    the replacement is not equivalent, and it causes PR 20627.  This patch
    is just to revert that change.

    Regression testing it on x86_64-linux.

    gdb/gdbserver:

    2016-09-30  Yao Qi  <yao.qi@linaro.org>

        PR gdbserver/20627
        * target.c (target_stop_and_wait): Don't call
        target_continue_no_signal, use resume_stop instead.

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

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]