public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppluzhnikov at google dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/12077] New: strncmp over-reads its buffer, may cause SIGSEGV Date: Fri, 01 Oct 2010 12:01:00 -0000 [thread overview] Message-ID: <20101001120105.12077.ppluzhnikov@google.com> (raw) Attached test case crashes in 64-bit mode ./a.out $j ./a.out $j 1 for all values of $j between 1 and 15 It does not crash in 32-bit mode (the bug appears to be in sysdeps/x86_64/strcmp.S). The bug is not present in glibc-2.7; is present in 2.11.1 and current trunk. -- Summary: strncmp over-reads its buffer, may cause SIGSEGV Product: glibc Version: unspecified Status: NEW Severity: critical Priority: P2 Component: libc AssignedTo: drepper dot fsp at gmail dot com ReportedBy: ppluzhnikov at google dot com CC: glibc-bugs at sources dot redhat dot com GCC build triplet: x86_64-linux-gnu GCC host triplet: x86_64-linux-gnu GCC target triplet: x86_64-linux-gnu http://sourceware.org/bugzilla/show_bug.cgi?id=12077 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2010-10-01 12:01 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-10-01 12:01 ppluzhnikov at google dot com [this message] 2010-10-01 12:04 ` [Bug libc/12077] " ppluzhnikov at google dot com 2010-10-01 13:23 ` drepper dot fsp at gmail dot com 2010-10-01 14:01 ` ppluzhnikov at google dot com 2010-10-01 17:14 ` ppluzhnikov at google dot com 2010-10-03 3:12 ` drepper dot fsp at gmail dot com 2010-10-03 3:23 ` ppluzhnikov at google dot com 2010-10-04 2:11 ` drepper dot fsp at gmail 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=20101001120105.12077.ppluzhnikov@google.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: linkBe 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).