public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nsz at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug malloc/27237] deadlock in malloc/tst-malloc-stats-cancellation
Date: Wed, 27 Jan 2021 09:41:47 +0000 [thread overview]
Message-ID: <bug-27237-131-ztEF3xBvCV@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27237-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27237
--- Comment #7 from Szabolcs Nagy <nsz at gcc dot gnu.org> ---
_IO_stdin_used is defined in csu/init.c which is built as
gcc init.c -c -std=gnu11 -fgnu89-inline -O2 [...] -D_LIBC_REENTRANT -include
/work/build/libc-modules.h -DMODULE_NAME=libc -include
../include/libc-symbols.h -DPIC -DTOP_NAMESPACE=glibc -o
/work/build/csu/init.o [...]
i think it should have -DLIBC_NONSHARED=1 since crt files end up in dynamic
linked binaries, so that's the actual bug.
on new targets _IO_stdin_used is unused (it's for bw compat with < glibc 2.1).
and the reason i could not reproduce this on i386 is that my gcc is multi
arch and then NO_HIDDEN_EXTERN_FUNC_IN_PIE is set, so the visibility pragma
is not present.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-01-27 9:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 11:01 [Bug malloc/27237] New: " schwab@linux-m68k.org
2021-01-25 17:20 ` [Bug malloc/27237] " nsz at gcc dot gnu.org
2021-01-25 18:26 ` schwab@linux-m68k.org
2021-01-26 18:18 ` nsz at gcc dot gnu.org
2021-01-26 18:29 ` schwab@linux-m68k.org
2021-01-26 18:56 ` schwab@linux-m68k.org
2021-01-27 9:21 ` schwab@linux-m68k.org
2021-01-27 9:41 ` nsz at gcc dot gnu.org [this message]
2021-01-27 11:30 ` cvs-commit at gcc dot gnu.org
2021-01-27 13:32 ` tuliom at ascii dot art.br
2021-01-28 14:07 ` 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-27237-131-ztEF3xBvCV@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: link
Be 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).