public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug threads/27239] gdb/cp-support.c:1619:(.text+0x5502): relocation truncated to fit: R_X86_64_PC32 against undefined symbol `TLS init function for thread_local_segv_handler' Date: Fri, 12 Mar 2021 17:22:05 +0000 [thread overview] Message-ID: <bug-27239-4717-djJUGp5bdw@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27239-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27239 --- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Christian Biesinger <cbiesinger@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=fece451c2aca57b095e7e4063e342781cf74aa75 commit fece451c2aca57b095e7e4063e342781cf74aa75 Author: Christian Biesinger <cbiesinger@google.com> Date: Tue Mar 9 08:16:23 2021 -0600 Use RAII to set the per-thread SIGSEGV handler This avoids using a thread-local extern variable, which causes link errors on some platforms, notably Cygwin. But I think this is a better pattern even outside of working around linker bugs because it encapsulates direct access to the variable inside the class, instead of having a global extern variable. The cygwin link error is: cp-support.o: in function `gdb_demangle(char const*, int)': /home/Christian/binutils-gdb/obj/gdb/../../gdb/cp-support.c:1619:(.text+0x6472): relocation truncated to fit: R_X86_64_PC32 against undefined symbol `TLS init function for thread_local_segv_handler' /home/Christian/binutils-gdb/obj/gdb/../../gdb/cp-support.c:1619:(.text+0x648b): relocation truncated to fit: R_X86_64_PC32 against undefined symbol `TLS init function for thread_local_segv_handler' collect2: error: ld returned 1 exit status 2021-03-12 Christian Biesinger <cbiesinger@google.com> PR threads/27239 * cp-support.c: Use scoped_segv_handler_restore. * event-top.c (thread_local_segv_handler): Made static. (scoped_segv_handler_restore::scoped_segv_handler_restore): New function. (scoped_segv_handler_restore::~scoped_segv_handler_restore): New function. * event-top.h (class scoped_segv_handler_restore): New class. (thread_local_segv_handler): Removed. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-12 17:22 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-25 13:25 [Bug threads/27239] New: " cbiesinger at google dot com 2021-01-25 13:25 ` [Bug threads/27239] " cbiesinger at google dot com 2021-01-25 17:39 ` ssbssa at sourceware dot org 2021-03-12 14:20 ` tromey at sourceware dot org 2021-03-12 17:22 ` cvs-commit at gcc dot gnu.org [this message] 2021-03-12 17:29 ` cvs-commit at gcc dot gnu.org 2021-03-13 12:57 ` cbiesinger at google dot com 2021-06-27 17:47 ` ahmedsayeed1982 at yahoo dot com 2021-08-10 11:45 ` ucelsanicin at yahoo dot com 2021-08-27 17:57 ` ribevi6798 at enamelme dot com 2021-08-28 18:31 ` buranlevent at yahoo dot com 2021-08-28 18:38 ` mark at klomp dot org 2021-09-06 9:10 ` focixujo at livinginsurance dot co.uk 2021-09-10 19:40 ` mehmetgelisin at aol dot com 2021-09-14 17:29 ` johnb6174 at gmail dot com 2021-09-26 13:31 ` tes.vik1986 at gmail dot com 2021-10-09 11:00 ` gulsenenginar at aol dot com 2021-10-10 16:10 ` oficaj3 at gmail dot com 2021-10-18 19:58 ` ahmedsayeed1982 at hotmail dot com 2021-10-19 7:14 ` progonsaytu at gmail dot com 2021-10-23 13:46 ` fiteva5725 at bomoads dot com 2021-10-24 10:02 ` glassmtech at ukr dot net 2021-10-29 10:57 ` kimolsun2020 at outlook dot com 2021-10-29 12:07 ` huracantili20 at gmail dot com 2021-11-02 15:21 ` gepaw63633 at dukeoo dot com 2021-11-06 21:12 ` paneki8601 at dukeoo dot com 2021-11-16 19:05 ` xecana8007 at funboxcn dot com 2021-11-16 19:08 ` xecana8007 at funboxcn dot com 2021-11-22 7:37 ` gexed96894 at keagenan 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-27239-4717-djJUGp5bdw@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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).