Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: Yao Qi <qiyaoltc@gmail.com>,
	 gdb-patches@sourceware.org,  simon.marchi@ericsson.com
Subject: Re: Move threads out of jumppad without single step
Date: Tue, 01 Dec 2015 11:36:00 -0000	[thread overview]
Message-ID: <864mg2v1s5.fsf@gmail.com> (raw)
In-Reply-To: <565C6043.4040106@redhat.com> (Pedro Alves's message of "Mon, 30	Nov 2015 14:42:11 +0000")

Pedro Alves <palves@redhat.com> writes:

> You may be able to handle this by retrieving state from the saved registers
> buffer in the jump pad, similar to how gdb_collect cooks up a regcache, though
> unlike gdb_collect, you'll have to handle the case of the thread stopping
> midway through that register saving too (some registers already saved, some 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.

-- 
Yao (齐尧)


  parent reply	other threads:[~2015-12-01 11:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-27 10:55 Yao Qi
2015-11-30 14:42 ` Pedro Alves
2015-11-30 19:04   ` Simon Marchi
2015-11-30 19:39     ` Pedro Alves
2015-12-01 11:36   ` Yao Qi [this message]
2016-01-27 16:47     ` Antoine Tremblay
2016-01-29 20:43       ` Antoine Tremblay
2016-02-04 16:58         ` Yao Qi
2016-02-04 18:24           ` Antoine Tremblay

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=864mg2v1s5.fsf@gmail.com \
    --to=qiyaoltc@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=simon.marchi@ericsson.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox