From: Tejun Heo <tj@kernel.org>
To: Denys Vlasenko <vda.linux@googlemail.com>
Cc: Oleg Nesterov <oleg@redhat.com>,
Jan Kratochvil <jan.kratochvil@redhat.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Merging ptrace branch into mainline
Date: Fri, 22 Jul 2011 15:39:07 +0200 [thread overview]
Message-ID: <20110722133907.GL2622@htj.dyndns.org> (raw)
In-Reply-To: <CAK1hOcPPyu7Q_o9JAj8VnGkhUShFFc+T1aYsKmhGhho2ykOD6Q@mail.gmail.com>
On Fri, Jul 22, 2011 at 01:40:36PM +0200, Denys Vlasenko wrote:
> On Fri, Jul 22, 2011 at 12:30 PM, Tejun Heo <tj@kernel.org> wrote:
> To what cases of ptrace stops is this applicable?
>
> I thought with PTRACE_O_TRACESYSGOOD the problem with SIGTRAP
> being special under strace is dealt with: now both user-sent
> SIGTRAPs and ones generated by int3 instruction are handled correctly
> in current strace git.
>
> Is it about single-stepping? Strace doesn't use PTRACE_SIGLESTEP,
> and I didn't have the need yet to familiarize myself with it.
> Does it generate SIGTRAP?
Single step and breakpoints use SIGTRAP and there are some variances
on the information being reported depending on archs and IIRC it isn't
always possible to discern those debug traps from kill(SIGTRAP)'s from
userland. I think cleaning up what information is reported via
siginfo on debug traps should resolve this too.
Thansk.
--
tejun
next prev parent reply other threads:[~2011-07-22 13:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 10:30 Tejun Heo
2011-07-22 11:40 ` Denys Vlasenko
2011-07-22 13:39 ` Tejun Heo [this message]
2011-07-22 14:59 ` Oleg Nesterov
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=20110722133907.GL2622@htj.dyndns.org \
--to=tj@kernel.org \
--cc=jan.kratochvil@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=vda.linux@googlemail.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
all inboxes | Powered by JetHome®