From: Pedro Alves <palves@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC PATCH] Appease Valgrind over ptrace calls.
Date: Thu, 14 Feb 2013 18:41:00 -0000 [thread overview]
Message-ID: <511D2FD3.3010305@redhat.com> (raw)
In-Reply-To: <20130214183800.4809.80774.stgit@brno.lan>
On 02/14/2013 06:38 PM, Pedro Alves wrote:
> Hmm, but, I'm now wondering why we don't see many more ptrace-related
> warnings in other cases. Maybe Valgrind does know about ptrace, but
> not about PTRACE_GETREGSET?
Found it... https://bugs.kde.org/show_bug.cgi?id=308886
Answer is yes. Valgrind doesn't know about PTRACE_GETREGSET. Issue
seems to be fixed upstream.
Dropping this patch.
Thanks for listening. :-)
--
Pedro Alves
prev parent reply other threads:[~2013-02-14 18:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 18:38 Pedro Alves
2013-02-14 18:41 ` Pedro Alves [this message]
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=511D2FD3.3010305@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
/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