public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug locale/31143] Let iconv_open return EMFILE if RLIMIT_NOFILE is hit Date: Tue, 12 Dec 2023 09:26:56 +0000 [thread overview] Message-ID: <bug-31143-131-7TKkYs582k@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31143-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31143 Florian Weimer <fweimer at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |22040 CC| |fweimer at redhat dot com --- Comment #1 from Florian Weimer <fweimer at redhat dot com> --- This depends on accurate tracking of errno values from system calls during dlopen (and, ugh, dlsym). Referenced Bugs: https://sourceware.org/bugzilla/show_bug.cgi?id=22040 [Bug 22040] dlopen: Provide more information on the root cause of a failure -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2023-12-12 9:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-12 2:00 [Bug locale/31143] New: " jengelh at inai dot de 2023-12-12 9:26 ` fweimer 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=bug-31143-131-7TKkYs582k@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /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).