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 dynamic-link/28503] New: dl_iterate_phdr namespace violation Date: Wed, 27 Oct 2021 06:23:44 +0000 [thread overview] Message-ID: <bug-28503-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=28503 Bug ID: 28503 Summary: dl_iterate_phdr namespace violation Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: dynamic-link Assignee: unassigned at sourceware dot org Reporter: fweimer at redhat dot com Target Milestone: --- The program below aborts even though it does nothing wrong. The reason is that the libgcc_s unwinder calls dl_iterate_phdr, which is not in the implementation namespace, so the application should be able to define it in a different way. #define _POSIX_SOURCE #include <pthread.h> #include <stdio.h> #include <stdlib.h> void dl_iterate_phdr (void) { abort (); } static void * thread_func (void *ignored) { pthread_exit (NULL); return NULL; } int main (void) { pthread_t thr; if (pthread_create (&thr, NULL, thread_func, NULL) != 0) { puts ("pthread_create failed"); return 1; } if (pthread_join (thr, NULL) != 0) { puts ("pthread_join failed"); return 1; } return 0; } -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-10-27 6:23 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-27 6:23 fweimer at redhat dot com [this message] 2021-12-28 21:55 ` [Bug dynamic-link/28503] " cvs-commit at gcc dot gnu.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-28503-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).