[Bug threads/14618] gdbserver also exits after a thread exits if"set scheduler-locking on"

["tom.tan at analog dot com" <sourceware-bugzilla at sourceware dot org>]

http://sourceware.org/bugzilla/show_bug.cgi?id=14618

Tom Tan <tom.tan at analog dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|scheduler-locking doesn't   |gdbserver also exits after
                   |work with gdbserver         |a thread exits if "set
                   |                            |scheduler-locking on"

--- Comment #2 from Tom Tan <tom.tan at analog dot com> 2012-09-26 07:58:29 UTC ---
Sorry, the title really doesn't describe the problem accurately. And thanks
Pedro for the wiki page, I missed that doc.

In no-unwaited-for-left.exp, if scheduler-locking is set to be "on", then after
the running thread exits, GDB server exits instead of the inferior is
resumed(my former description is not exact either). I set a break point after
the new thread exits and it doesn't execute to that code. 

I followed the code a bit and found that the last_status of gdbserver is
TARGET_WAITKIND_EXITED after the thread exits, then the process is mourned.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.