public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aurelien at aurel32 dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/110066] [RISC-V] Segment fault if compiled with -static -pg Date: Fri, 21 Jul 2023 16:21:17 +0000 [thread overview] Message-ID: <bug-110066-4-NHEhDxNcGH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110066-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110066 Aurelien Jarno <aurelien at aurel32 dot net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aurelien at aurel32 dot net --- Comment #4 from Aurelien Jarno <aurelien at aurel32 dot net> --- This is also reproducible with the tst-gmon-static test from glibc 2.38, when compiled with GCC 13, while the test passes fine with GCC 12. A very basic debugging shows that the problem is triggered by using crtbeginT.o from GCC 13. The test passes when compiling everything with GCC 13, but using crtbeginT.o from GCC 12. The backtrace is the following: Program received signal SIGSEGV, Segmentation fault. 0x00000000000516e2 in classify_object_over_fdes () (gdb) bt #0 0x00000000000516e2 in classify_object_over_fdes () #1 0x0000000000052690 in __register_frame_info () #2 0x0000000000010570 in frame_dummy () #3 0x0000000000010872 in call_init (envp=0x3ffffff3e0, argv=0x3ffffff3c8, argc=2) at libc-start.c:189 #4 __libc_start_main_impl (main=0x10448 <main>, argc=2, argv=0x3ffffff3c8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=<optimized out>) at libc-start.c:355 #5 0x0000000000010488 in _start () at ../sysdeps/riscv/start.S:61
next prev parent reply other threads:[~2023-07-21 16:21 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-31 20:36 [Bug target/110066] New: " i at rvalue dot moe 2023-05-31 20:39 ` [Bug target/110066] " pinskia at gcc dot gnu.org 2023-05-31 21:00 ` schwab@linux-m68k.org 2023-05-31 22:35 ` i at rvalue dot moe 2023-07-21 16:21 ` aurelien at aurel32 dot net [this message] 2023-07-22 5:16 ` pinskia at gcc dot gnu.org 2023-07-22 5:18 ` pinskia at gcc dot gnu.org 2023-07-22 8:46 ` aurelien at aurel32 dot net 2023-07-22 8:46 ` aurelien at aurel32 dot net 2023-07-22 8:47 ` aurelien at aurel32 dot net 2023-07-22 12:37 ` aurelien at aurel32 dot net 2023-07-22 14:50 ` aurelien at aurel32 dot net 2023-07-22 15:30 ` aurelien at aurel32 dot net 2023-07-22 15:53 ` [Bug target/110066] [13/14 Regression] " pinskia at gcc dot gnu.org 2023-07-22 15:56 ` pinskia at gcc dot gnu.org 2023-07-22 16:57 ` aurelien at aurel32 dot net 2023-07-22 17:02 ` pinskia at gcc dot gnu.org 2023-07-22 17:32 ` schwab@linux-m68k.org 2023-07-22 17:36 ` aurelien at aurel32 dot net 2023-07-22 17:36 ` schwab@linux-m68k.org 2023-07-22 20:32 ` pinskia at gcc dot gnu.org 2023-07-23 1:07 ` pinskia at gcc dot gnu.org 2023-07-23 4:55 ` cvs-commit at gcc dot gnu.org 2023-07-23 4:57 ` [Bug target/110066] [13 " pinskia at gcc dot gnu.org 2023-07-27 9:26 ` rguenth at gcc dot gnu.org 2023-08-04 11:15 ` aurelien at aurel32 dot net 2023-09-04 6:26 ` i at rvalue dot moe 2024-05-08 16:08 ` cvs-commit at gcc dot gnu.org 2024-05-08 16:08 ` pinskia 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-110066-4-NHEhDxNcGH@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).