public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "chris2k01 at hotmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/11100] New: sysdeps/unix/sysv/linux/ptrace.c PTRACE_SETOPTIONS inappropriate pointer check
Date: Wed, 16 Dec 2009 22:11:00 -0000	[thread overview]
Message-ID: <20091216221117.11100.chris2k01@hotmail.com> (raw)

In sysdeps/unix/sysv/linux/ptrace.c, on line 102, if __BOUNDED__POINTERS__ is 
true, checks are done that pointers point at appropriate locations. Such a 
check is done on the "data" argument to ptrace() if the "request" argument is 
PTRACE_SETOPTIONS. However, according to ptrace(2) (and, indeed, according to 
the gdb sources and the kernel sources), the PTRACE_SETOPTIONS request accepts 
a bitmask of PTRACE_O_* values as its "data" argument, *not* a pointer.

-- 
           Summary: sysdeps/unix/sysv/linux/ptrace.c PTRACE_SETOPTIONS
                    inappropriate pointer check
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: minor
          Priority: P2
         Component: libc
        AssignedTo: drepper at redhat dot com
        ReportedBy: chris2k01 at hotmail dot com
                CC: glibc-bugs at sources dot redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=11100

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2009-12-16 22:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-16 22:11 chris2k01 at hotmail dot com [this message]
2010-04-05  4:30 ` [Bug libc/11100] " drepper at redhat dot com
2010-04-05  8:12 ` chris2k01 at hotmail dot com

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=20091216221117.11100.chris2k01@hotmail.com \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).