public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "drepper at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/3355] strnlen() accesses memory locations beyond (s + maxlen)
Date: Fri, 13 Oct 2006 04:31:00 -0000	[thread overview]
Message-ID: <20061013043104.2095.qmail@sourceware.org> (raw)
In-Reply-To: <20061012145036.3355.kris.van.hees@oracle.com>


------- Additional Comments From drepper at redhat dot com  2006-10-13 04:31 -------
There is no bug anywhere except in your understanding what the runtime is
supposed to do.

-- 


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

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


      parent reply	other threads:[~2006-10-13  4:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-12 14:50 [Bug libc/3355] New: " kris dot van dot hees at oracle dot com
2006-10-12 14:52 ` [Bug libc/3355] " kris dot van dot hees at oracle dot com
2006-10-12 20:48 ` drepper at redhat dot com
2006-10-12 23:48 ` kris dot van dot hees at oracle dot com
2006-10-13  4:31 ` drepper at redhat dot com [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=20061013043104.2095.qmail@sourceware.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).