llvm-bolt --instrument error crash

[zhouyu0502]

1. i want llvm-bolt a shared library for arm64
2. llvm-bolt camera.qcom.so --instrument -o camera.qcom.instr.so
   this camera.qcom.so is from a camera using qcom chip

[llvmbot]

@llvm/issue-subscribers-bolt

Author: None (zhouyu0502)

1. i want llvm-bolt a shared library for arm64 2. llvm-bolt camera.qcom.so --instrument -o camera.qcom.instr.so this camera.qcom.so is from a camera using qcom chip <img width="2939" height="775" alt="Image" src="https://github.com/user-attachments/assets/e2597c5f-ffcf-441f-9591-01376f9240d1" />

[yavtuk]

@zhouyu0502 can you provide a reproducer? If not you can add more verbosity to output using -v 2 or/and --debug options

[zhouyu0502]

i have add some logs and make sure that this crash is because in function RewriteInstance::handleRelocation, ContainingBF is nullptr after initialize. I still work on this bug

[yavtuk]

Which one compiler and linker do you use?

[yavtuk]

Let's check the original relocations
readelf -Wr ./bin

[zhouyu0502]

Let's check the original relocations readelf -Wr ./bin
this file is 180M too big ,wihch section do you want?
this is the init section which need debug according the following analysis

2.i have add some logs here

and i find when handling section .rela.init it shows it can not find function in address 0x384114 because the BinaryFunctions key is from 0x384130 to 0x15bed60, and i add return temporarily when this happens

[zhouyu0502]

Which one compiler and linker do you use?

i want to use bolt to instrument shared liobraries (arm64) ,but i use llvm-bolt in my server which is x86_64.
the shared liobraries camera.qcom.so is from aosp and use gcc11.5 and

[zhouyu0502]

after i finish the first crash (add return when ConteningBF is nullptr), i come across another crash
here are the detailed information
1.compile bolt in -DCMAKE_BUILD_TYPE=Debug
2.instrument
2.1 run llvm-bolt camera.qcom.so --instrument -o camera.qcom.so.instr

log show here

2.2 run llvm-bolt camera.qcom.so -v=2 --instrument -o camera.qcom.so.instr

BOLT-WARNING: FDE [0x3881f0, 0x388234) has no corresponding symbol table entry
......<5207 line omitted>
BOLT-WARNING: FDE [0x15bde60, 0x15be020) has no corresponding symbol table entry

BOLT-INFO: setting size of function _BOLT_PSEUDO.plt to 32 (was 0)
......<1022 line omitted>
BOLT-INFO: setting size of function xxxxxx

BOLT-INFO: potentially escaped address 0x6f280c in function xxxx
......<649 line omitted>
BOLT-INFO: potentially escaped address 0x15b6188 in function xxx

3.when i use .compile bolt in -DCMAKE_BUILD_TYPE=Release
log shows

[paschalis-mpeis]

Regarding the follow-up crash: we are adding support for PAC-RET security hardening, you may subscribe here for updates:

• [BOLT][AArch64] Handle OpNegateRAState to enable optimizing binaries with pac-ret hardening #120064

On your setup: so you have an AArch64 shared lib and you cross-bolt it on your X86 machine?
Does this work out of the box, or are you applying some custom patch for this (ie #101180)?

(@bgergely0)

[zhouyu0502]

Regarding the follow-up crash: we are adding support for PAC-RET security hardening, you may subscribe here for updates:

• [BOLT][AArch64] Handle OpNegateRAState to enable optimizing binaries with pac-ret hardening #120064

On your setup: so you have an AArch64 shared lib and you cross-bolt it on your X86 machine? Does this work out of the box, or are you applying some custom patch for this (ie #101180)?

(@bgergely0)

thanks for your answer

yes i have cross-bolt it on your X86 machine by modifying bolt runtime CMakeLists and ets, it works ok for so and bin