public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vapier at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/2386] New: ia64/clone2: make sure child_stack is non-NULL
Date: Thu, 23 Feb 2006 03:12:00 -0000	[thread overview]
Message-ID: <20060223031252.2386.vapier@gentoo.org> (raw)

playing with uClibc/ia64 and i noticed that a test case we have for testing 
the return value of clone() when given bum arguments was failing ... seems 
the clone2() function in ia64 never verifies child_stack like all other 
architectures

attached patch adds a check for child_stack alongside the check for 
child_fn ... i know squat about ia64 assembly so i'd be surprised if this was 
correct :)

also, this is the first test case ive written for glibc, so it too may have quirks

-- 
           Summary: ia64/clone2: make sure child_stack is non-NULL
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: drepper at redhat dot com
        ReportedBy: vapier at gentoo dot org
                CC: glibc-bugs at sources dot redhat dot com,hjl at lucon
                    dot org
  GCC host triplet: ia64-linux


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

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


             reply	other threads:[~2006-02-23  3:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-23  3:12 vapier at gentoo dot org [this message]
2006-02-23  3:13 ` [Bug libc/2386] " vapier at gentoo dot org
2006-04-25 19:15 ` drepper at redhat 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=20060223031252.2386.vapier@gentoo.org \
    --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).