From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 109548 invoked by alias); 1 Dec 2015 11:36:38 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 109532 invoked by uid 89); 1 Dec 2015 11:36:37 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-pa0-f49.google.com Received: from mail-pa0-f49.google.com (HELO mail-pa0-f49.google.com) (209.85.220.49) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Tue, 01 Dec 2015 11:36:37 +0000 Received: by pacej9 with SMTP id ej9so3059815pac.2 for ; Tue, 01 Dec 2015 03:36:35 -0800 (PST) X-Received: by 10.66.164.196 with SMTP id ys4mr98700258pab.119.1448969795472; Tue, 01 Dec 2015 03:36:35 -0800 (PST) Received: from E107787-LIN (gcc1-power7.osuosl.org. [140.211.15.137]) by smtp.gmail.com with ESMTPSA id g79sm57378451pfj.13.2015.12.01.03.36.30 (version=TLS1_2 cipher=AES128-SHA bits=128/128); Tue, 01 Dec 2015 03:36:34 -0800 (PST) From: Yao Qi To: Pedro Alves Cc: Yao Qi , gdb-patches@sourceware.org, simon.marchi@ericsson.com Subject: Re: Move threads out of jumppad without single step References: <86zixzvhj1.fsf@gmail.com> <565C6043.4040106@redhat.com> Date: Tue, 01 Dec 2015 11:36:00 -0000 In-Reply-To: <565C6043.4040106@redhat.com> (Pedro Alves's message of "Mon, 30 Nov 2015 14:42:11 +0000") Message-ID: <864mg2v1s5.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2015-12/txt/msg00002.txt.bz2 Pedro Alves writes: > You may be able to handle this by retrieving state from the saved registe= rs > buffer in the jump pad, similar to how gdb_collect cooks up a regcache, t= hough > unlike gdb_collect, you'll have to handle the case of the thread stopping > midway through that register saving too (some registers already saved, so= me not > yet). Compute the next PCs on the basis of cooked up regcache from stack is what I intended, but I didn't consider the case thread is stopped in the middle way of register saving. > > So I assume it's much simpler to just run to [1] as well, and then issue > a normal software single-step when you get there. Then, looks we have to use software single step. --=20 Yao (=E9=BD=90=E5=B0=A7)