public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@openvz.org>
To: Pedro Alves <palves@redhat.com>
Cc: Oleg Nesterov <oleg@redhat.com>,
	Pavel Emelyanov <xemul@parallels.com>,
	Jan Kratochvil <jan.kratochvil@redhat.com>,
	Tejun Heo <tj@kernel.org>, Andrew Vagin <avagin@openvz.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ptrace: add ability to get clear_tid_address
Date: Wed, 8 Feb 2012 00:56:39 +0400	[thread overview]
Message-ID: <20120207205639.GJ27437@moon> (raw)
In-Reply-To: <4F31848A.9070406@redhat.com>

On Tue, Feb 07, 2012 at 08:07:38PM +0000, Pedro Alves wrote:
> On 02/03/2012 04:51 PM, Oleg Nesterov wrote:
> > On 02/03, Pavel Emelyanov wrote:
> 
> >> Because there's no need for current to get this value of himself, but can
> >> be useful for e.g. gdb.
> > 
> > OK, perhaps this makes sense, I do not know.
> > 
> > Jan, Pedro, do you think gdb can use PTRACE_GET_TID_ADDRESS (returns
> > tracee->clear_child_tid) ?
> 
> Off hand, I'm not picturing a use.  But that may well just mean I'm lacking
> imagination.  Andrew, Pavel, did you have a particular idea in mind when you
> said it may be useful for debugging a multithreading program / gdb?
> 

Might not we set up hw watchpoint on this address and get interrupt
before pthread-join will find it? (To be fair I'm not sure if such
trick will work, didn't test ;)

	Cyrill

  reply	other threads:[~2012-02-07 20:56 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-03 11:11 [PATCH] ptrace: add ability to get clear_tid_address Andrew Vagin
2012-02-03 16:25 ` Tejun Heo
2012-02-03 16:30   ` Cyrill Gorcunov
2012-02-03 16:41     ` Oleg Nesterov
2012-02-03 16:54       ` Cyrill Gorcunov
2012-02-03 16:45   ` Pavel Emelyanov
2012-02-03 16:51     ` Oleg Nesterov
2012-02-07 20:07       ` Pedro Alves
2012-02-07 20:56         ` Cyrill Gorcunov [this message]
2012-02-07 21:15           ` Pedro Alves
2012-02-07 21:51             ` Cyrill Gorcunov
2012-02-08 12:30               ` Pedro Alves
2012-02-08 12:42                 ` Cyrill Gorcunov
2012-02-08 17:31                 ` Oleg Nesterov
2012-02-08 18:04                   ` Pedro Alves
2012-02-08 19:02                     ` Oleg Nesterov
2012-02-08 19:20                       ` Cyrill Gorcunov
2012-02-08 19:21                       ` Jan Kratochvil
2012-02-08 19:42                       ` Pedro Alves
2012-02-08 13:41         ` Andrew Vagin
2012-02-08 18:12           ` Jan Kratochvil
2012-02-10  3:02             ` Jamie Lokier

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=20120207205639.GJ27437@moon \
    --to=gorcunov@openvz.org \
    --cc=avagin@openvz.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=palves@redhat.com \
    --cc=tj@kernel.org \
    --cc=xemul@parallels.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