[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug ld/31954] [ld] [lto] [clang] using ld and lto, crash while dynamic
From: |
nickc at redhat dot com |
Subject: |
[Bug ld/31954] [ld] [lto] [clang] using ld and lto, crash while dynamic compile executable |
Date: |
Tue, 06 Aug 2024 10:36:11 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=31954
--- Comment #4 from Nick Clifton <nickc at redhat dot com> ---
Hi Hanwei,
Thanks for uploading the object files. As I suspected however, on their own
they are not enough to trigger the bug. For example a I tried test, based upon
the command line you provided, but with the system files and libraries removed,
and it worked:
$ ld -pie --be8 -EB -z relro --hash-style=gnu --eh-frame-hdr -m
armelfb_linux_eabi -o g++-dg-lto-200811125.exe -plugin /usr/lib64/LLVMgold.so
-plugin-opt=mcpu=generic cp_lto_20081125_0.o cp_lto_20081125_1.o -e 0
$ echo $?
0
I suspect that the problem is related to the fact that you are targeting a
big-endian ARM system. (The little-endian version tends to get more testing
than the big-endian version).
Given that you do have the full linker command line available, are you able to
run the linker under GDB and find out where the seg-fault is happening ? And
what is causing it ? A null pointer ? Accessing freed memory ? Something else
?
Cheers
Nick
--
You are receiving this mail because:
You are on the CC list for the bug.
- [Bug ld/31954] [ld] [lto] [clang] using ld and lto, crash while dynamic compile executable, nickc at redhat dot com, 2024/08/02
- [Bug ld/31954] [ld] [lto] [clang] using ld and lto, crash while dynamic compile executable, hanwei62 at huawei dot com, 2024/08/05
- [Bug ld/31954] [ld] [lto] [clang] using ld and lto, crash while dynamic compile executable, hanwei62 at huawei dot com, 2024/08/05
- [Bug ld/31954] [ld] [lto] [clang] using ld and lto, crash while dynamic compile executable,
nickc at redhat dot com <=
- [Bug ld/31954] [ld] [lto] [clang] using ld and lto, crash while dynamic compile executable, zhenhangwang at huawei dot com, 2024/08/06