public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "adhemerval.zanella at linaro dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/30350] Deadlock flush - malloc - fork - fgets Date: Thu, 13 Apr 2023 20:04:38 +0000 [thread overview] Message-ID: <bug-30350-131-IOD7v8zNMw@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30350-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30350 Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adhemerval.zanella at linaro dot o | |rg --- Comment #1 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> --- Does it happen with 2.36 or master? Do you have a testcase to reproduce it, even in a non-deterministic manner? It is really hard to debug such issues, specially with backtraces from quite old version (fork has been refactored with multiple fixes, and lowlevellock.S has been removed). -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-04-13 20:04 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-13 19:54 [Bug libc/30350] New: " 7i77an at gmail dot com 2023-04-13 20:04 ` adhemerval.zanella at linaro dot org [this message] 2023-04-13 20:40 ` [Bug libc/30350] " 7i77an at gmail dot com 2023-04-13 20:45 ` adhemerval.zanella at linaro dot org 2023-04-17 18:00 ` 7i77an at gmail dot com 2023-04-20 20:16 ` adhemerval.zanella at linaro dot org
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-30350-131-IOD7v8zNMw@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).