From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libelf/28190] FAIL: run-backtrace-native.sh with glibc 2.34
Date: Wed, 04 Aug 2021 18:56:42 +0000 [thread overview]
Message-ID: <bug-28190-10460-pGOBKJgUTr@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28190-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28190
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2021-08-04
Status|UNCONFIRMED |ASSIGNED
--- Comment #2 from Mark Wielaard <mark at klomp dot org> ---
This comes from the following glibc commit:
commit f779b1efb35fe141e47952af3ac7f0540acca401
Author: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Date: Mon Dec 7 16:21:55 2020 -0300
nptl: Implement raise in terms of pthread_kill
Now that pthread_kill is provided by libc.so it is possible to
implement the generic POSIX implementation as
'pthread_kill(pthread_self(), sig)'.
For Linux implementation, pthread_kill read the targeting TID from
the TCB. For raise, this it not possible because it would make raise
fail when issue after vfork (where creates the resulting process
has a different TID from the parent, but its TCB is not updated as
for pthread_create). To make raise use pthread_kill, it is make
usable from vfork by getting the target thread id through gettid
syscall.
Checked on x86_64-linux-gnu and aarch64-linux-gnu.
Before raise simply called the (tg)kill syscall directly. Now we have an extra
frame in the backtrace.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-08-04 18:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 14:32 [Bug libelf/28190] New: " mliska at suse dot cz
2021-08-04 17:13 ` [Bug libelf/28190] " richard.purdie at linuxfoundation dot org
2021-08-04 18:56 ` mark at klomp dot org [this message]
2021-08-04 19:04 ` mark at klomp dot org
2021-08-05 7:45 ` richard.purdie at linuxfoundation dot org
2021-08-05 11:06 ` mark at klomp dot org
2021-08-05 16:50 ` richard.purdie at linuxfoundation dot org
2021-08-05 17:09 ` mark at klomp dot org
2021-08-25 8:47 ` fweimer 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=bug-28190-10460-pGOBKJgUTr@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@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).