public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "yd-huang at outlook dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/26275] New: abort(3) is not signal-safe Date: Wed, 22 Jul 2020 04:31:36 +0000 [thread overview] Message-ID: <bug-26275-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=26275 Bug ID: 26275 Summary: abort(3) is not signal-safe Product: glibc Version: unspecified Status: UNCONFIRMED Severity: critical Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: yd-huang at outlook dot com CC: drepper.fsp at gmail dot com Target Milestone: --- abort(3) is required to be signal-safe by POSIX, but it's not, according to: 1. https://www.gnu.org/software/libc/manual/html_node/Aborting-a-Program.html#Aborting-a-Program 2. https://sourceware.org/git/?p=glibc.git;a=blob;f=stdlib/abort.c;h=df98782dd7ea6c1476184a365bd9f3954f481a18;hb=refs/heads/master#l54 -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2020-07-22 4:31 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-22 4:31 yd-huang at outlook dot com [this message] 2020-07-22 4:43 ` [Bug libc/26275] " yd-huang at outlook dot com 2020-08-11 17:30 ` yd-huang at outlook dot com 2020-08-11 22:45 ` jistone at redhat dot com 2020-08-12 0:26 ` carlos at redhat dot com 2020-08-12 7:24 ` yd-huang at outlook dot com 2020-09-24 21:46 ` carlos at redhat dot com 2020-09-27 14:21 ` carlos at redhat dot com 2020-09-27 16:38 ` yd-huang at outlook 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=bug-26275-131@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).