From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-prs-return-12343-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Received: (qmail 12834 invoked by alias); 26 Sep 2012 07:58:31 -0000
Received: (qmail 12807 invoked by uid 48); 26 Sep 2012 07:58:30 -0000
From: "tom.tan at analog dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/14618] gdbserver also exits after a thread exits if
 "set scheduler-locking on"
Date: Wed, 26 Sep 2012 07:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: threads
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: critical
X-Bugzilla-Who: tom.tan at analog dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields: Summary
Message-ID: <bug-14618-4717-7JuEAP9Gh8@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-14618-4717@http.sourceware.org/bugzilla/>
References: <bug-14618-4717@http.sourceware.org/bugzilla/>
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
X-SW-Source: 2012-q3/txt/msg00394.txt.bz2


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.