public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bruno at clisp dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/5346] New: gettext crashes when a very long string is passed as argument and the stack size is limited Date: Fri, 16 Nov 2007 01:22:00 -0000 [thread overview] Message-ID: <20071116012223.5346.bruno@clisp.org> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1838 bytes --] On most systems, the stack size is limited ("ulimit -s 8192" is often the default). In these conditions, gettext() crashes when the argument string is longer than the maximum stack size. This was reported in <http://www.securityfocus.com/archive/1/483648/30/30/threaded> and then reported to bug-gnu-gettext by Ismail Dönmez. Find attached a test case. ================================ foo.c ======================== #include <stdlib.h> #include <string.h> #include <sys/types.h> #include <sys/time.h> #include <sys/resource.h> #include <libintl.h> int main () { size_t n; struct rlimit limit; char *msg; n = 1000000; #ifdef RLIMIT_STACK if (getrlimit (RLIMIT_STACK, &limit) >= 0) { if (limit.rlim_max == RLIM_INFINITY || limit.rlim_max > n) limit.rlim_max = n; limit.rlim_cur = limit.rlim_max; setrlimit (RLIMIT_STACK, &limit); } #endif msg = (char *) malloc (n + 1); memset (msg, 'x', n); msg[n] = '\0'; msg = gettext (msg); return 0; } =============================================================== $ gcc -Wall foo.c $ ./a.out Segmentation fault -- Summary: gettext crashes when a very long string is passed as argument and the stack size is limited Product: glibc Version: 2.4 Status: NEW Severity: minor Priority: P2 Component: libc AssignedTo: drepper at redhat dot com ReportedBy: bruno at clisp dot org CC: glibc-bugs at sources dot redhat dot com GCC build triplet: i586-suse-linux GCC host triplet: i586-suse-linux GCC target triplet: i586-suse-linux http://sourceware.org/bugzilla/show_bug.cgi?id=5346 ------- 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:[~2007-11-16 1:22 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-11-16 1:22 bruno at clisp dot org [this message] 2007-11-16 1:24 ` [Bug libc/5346] " bruno at clisp dot org 2007-11-16 1:36 ` bruno at clisp dot org 2007-11-16 3:05 ` ismail at pardus dot org dot tr 2007-11-16 3:10 ` bruno at clisp dot org 2007-11-17 7:38 ` 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=20071116012223.5346.bruno@clisp.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).