public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nix at esperi dot org dot uk" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/7066] Probable buffer overrun in strtold() Date: Fri, 05 Dec 2008 00:18:00 -0000 [thread overview] Message-ID: <20081205001740.24058.qmail@sourceware.org> (raw) In-Reply-To: <20081204004909.7066.nix@esperi.org.uk> ------- Additional Comments From nix at esperi dot org dot uk 2008-12-05 00:17 ------- It's using the same compile line that glibc's 'make check' uses, which passes -std=gnu99 (IIRC: I don't have a build tree at the right point to verify this right now). The original testcase in glibc calls strtold() with many different inputs: only this one crashes under -fstack-protector-all, and the corrupted stack is not in the testing function but within glibc itself. So I don't see how e.g. pointer width differences (not applicable on x86-32 anyway as far as I can see) could cause a problem. It's not as if this is a varargs function on AIX or something. -- http://sourceware.org/bugzilla/show_bug.cgi?id=7066 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2008-12-05 0:18 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-12-04 0:50 [Bug libc/7066] New: " nix at esperi dot org dot uk 2008-12-04 12:13 ` [Bug libc/7066] " nix at esperi dot org dot uk 2008-12-04 14:09 ` pasky at suse dot cz 2008-12-05 0:18 ` nix at esperi dot org dot uk [this message] 2010-09-01 19:41 ` drepper at redhat dot com [not found] <bug-7066-131@http.sourceware.org/bugzilla/> 2014-07-01 20:59 ` fweimer 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=20081205001740.24058.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: 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).