public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "thomas dot jarosch at intra2net dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/5758] New: [patch] Fix getrlimit() acting funny sometimes Date: Tue, 12 Feb 2008 14:30:00 -0000 [thread overview] Message-ID: <20080212142925.5758.thomas.jarosch@intra2net.com> (raw) Hey there, attached patch fixes a little bug I found while tracing some getrlimit issues on my system. Please have a look, I couldn't find a place where "__have_no_new_getrlimit" seems to get initialized. The patch is still valid for glibc HEAD. Currently pthread_create fails on my system as ugetrlimit(STACK_SIZE) retuns "2147483648". That -almost- half the size of RLIM_INFINITY. mmap() in ntpl/allocatestack.c then tries to get 2GB of memory on my 1 GB box ;-) Still investigating... Cheers, Thomas -- Summary: [patch] Fix getrlimit() acting funny sometimes Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: drepper at redhat dot com ReportedBy: thomas dot jarosch at intra2net dot com CC: glibc-bugs at sources dot redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=5758 ------- 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:[~2008-02-12 14:30 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-02-12 14:30 thomas dot jarosch at intra2net dot com [this message] 2008-02-12 14:30 ` [Bug libc/5758] " thomas dot jarosch at intra2net dot com 2008-02-12 15:22 ` drepper at redhat dot com 2008-02-12 15:23 ` drepper at redhat dot com 2008-02-12 16:10 ` thomas dot jarosch at intra2net dot com 2008-02-12 18:41 ` thomas dot jarosch at intra2net dot com 2008-02-14 16:09 ` thomas dot jarosch at intra2net dot com 2008-03-09 5:49 ` 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=20080212142925.5758.thomas.jarosch@intra2net.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).