fix(android): symbolicate APK-embedded tombstone frames

[supervacuus]

📜 Description

Fix tombstone symbolication for native libraries loaded directly from uncompressed APK entries.

The parser now accepts ELF mappings with build IDs at nonzero APK offsets, distinguishes multiple ELFs sharing the same APK path, validates mapping continuations using the tombstone page size, and sets frame image_addr from pc - rel_pc.

Correction during review:

• ELF PT_LOAD virtual addresses and file offsets can diverge by one segment-alignment unit at each boundary. Meaning continuations must be validated relative to the previous mapping rather than the module start, so we don't accumulate drift (across multi-segment ELFs).
• The tolerance now also accounts for the case where 16 KiB-aligned ELFs run on 4 KiB devices (meaning ELF alignment would exceed the tombstone's reported runtime page size).

💡 Motivation and Context

TombstoneParser required mapping.offset == 0, excluding ELFs mapped from inside an APK. This removed their debug images when tombstone data replaced the original native event metadata, resulting in unknown_image.

But Android's libunwindstack already resolved the ELF and supplied its build ID, so Java doesn't need to reopen or parse the APK (as the Native SDK module loader does).

Fixes #5986.

💚 How did you test it?

I added the following test cases (names taken directly from the test module):

• creates images for multiple ELF files embedded in same APK: verifies distinct build IDs produce distinct images despite sharing base.apk.
• coalesces multiple ELF continuations aligned for 16 KiB pages: covers an ELF with three PT_LOAD mappings and verifies that per-segment alignment drift does not accumulate.
• does not include a different embedded ELF without build ID in previous image: prevents unrelated APK mappings from expanding the previous image.
• sets image address on frame for ELF embedded in APK: verifies image_addr is derived from pc - rel_pc.
• parses APK embedded ELF from full tombstone fixture: validates an Android 15 tombstone produced by a non-legacy packaging build (but only the relevant diffs to the default fixture are asserted and not a full snapshot test which would just duplicate most of the existing tests). Now also verifies complete module sizes for 16KiB-aligned ELFs captured on a 4KiB device.

Ran the tombstone tests.

Also "manually" compared the resulting envelopes when running from a non-legacy packaged sample build against the tombstone integration and the ndk integration (both now have the debug images for the APK, whereas previously they didn't).

📝 Checklist

• I added GH Issue ID & Linear ID
• I added tests to verify the changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• I updated the wizard if needed.
• Review from the native team if needed.
• No breaking change or entry added to the changelog.
• No breaking change for hybrid SDKs or communicated to hybrid SDKs.
• Public API changes reviewed by another Mobile SDK team member or implemented according to the develop docs spec.

🔮 Next steps

[sentry]

📲 Install Builds

Android

🔗 App Name	App ID	Version	Configuration
SDK Size	io.sentry.tests.size	8.53.0 (1)	release

⚙️ sentry-android Build Distribution Settings

[markushi]

Looks great, thank you!