Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose function to get address of dynamic instruction for Flutter crash symbolication #831

Open
ahmed24khaled opened this issue Mar 2, 2024 · 1 comment

Comments

@ahmed24khaled
Copy link

Hello folks,

I am trying to use Sentry's symbolic project to symbolicate Flutter crashes like below:

#00 abs 00000079069f28af virt 000000000038c8af _kDartIsolateSnapshotInstructions+0x246f2f
#01 abs 000000790691ab6f virt 00000000002b4b6f _kDartIsolateSnapshotInstructions+0x16f1ef

I'm having trouble getting the address of the dynamic instruction _kDartIsolateSnapshotInstructions that is needed for symbolication.

When I looked at the symbolication process in Flutter(symbolize command), I found that I need the address of the dynamic instruction and the address of the symbol will be instruction address + offset. However, I couldn't find an exposed function that returns the address based on the instruction.

I noticed that the information I need is available in the symbols, dynamic_symbols, and dynamic_strtab fields of the ELF file. Therefore, I'm wondering if it would be possible to expose a function that returns the address of the dynamic instruction for the purpose of symbolicating Flutter crashes.

If I'm missing something, could someone please help me understand how to get the address of the dynamic instruction for Flutter crash symbolication or how to use symbolic for this case ?

Also, I believe that the crashes sent from the Dart SDK have the same format as the one I provided above without the address of the instruction, right?

Thank you.

@loewenheim
Copy link
Contributor

Hi, thank you for the report. I'm putting this on the backlog for now; we don't have the bandwidth for this right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

2 participants