[Bolt]llvm-bolt instrument causes the system to crash and cannot start normally

[qianwindz]

instrumenting result

Logcat result of system startup failure

If you need any more data, please let me know

[llvmbot]

@llvm/issue-subscribers-bolt

Author: None (qianwindz)

instrumenting result <img width="685" height="970" alt="Image" src="https://github.com/user-attachments/assets/cd5dd8a3-6ae6-41eb-a181-5ccdc069b75a" /> Logcat result of system startup failure <img width="1058" height="1050" alt="Image" src="https://github.com/user-attachments/assets/81b5979b-d624-4d03-8e97-d4fe16758459" /> If you need any more data, please let me know

[bgergely0]

Hi! This is an AOSP library, isn't it?

I believe BOLT cannot properly process compressed debug sections. You can try the workaround patch from this comment: #147017 (comment)

[qianwindz]

Hi! This is an AOSP library, isn't it?

I believe BOLT cannot properly process compressed debug sections. You can try the workaround patch from this comment: #147017 (comment)

Okay, I'll give it a try

[qianwindz]

@bgergely0
Thank you very much. After I added the configuration and disabled the pac ret function, the so library after BOLT can now run normally, but it did not generate prof.fdata in the /tmp directory, even though the /tmp directory is writable.What could be the possible reason for this? Thank you very much.

[bgergely0]

@qianwindz taking a second look here: I believe the ILL_ILLOPC you are getting is from a Branch Target Exception. As the log says:
BOLT-WARNING: binary is using BTI. Optimized binary may be corrupted

To solve this, use -mbranch-protection=none or =pac-ret, but not =standard as that includes BTI.

[bgergely0]

it did not generate prof.fdata in the /tmp directory, even though the /tmp directory is writable.What could be the possible reason for this?

Not sure, I didn't use BOLT on AOSP much. But as that's a separate issue, it would be better to close this, and open a new one with details, as this will get hard to follow.

[qianwindz]

it did not generate prof.fdata in the /tmp directory, even though the /tmp directory is writable.What could be the possible reason for this?

Not sure, I didn't use BOLT on AOSP much. But as that's a separate issue, it would be better to close this, and open a new one with details, as this will get hard to follow.

Well, thank you very much.