Registers in native crashes not ordering numerically; seem to be lexicographic now

getsentry / sentry

Developer-first error tracking and performance monitoring

https://sentry.io

Other

39.23k stars 4.21k forks source link

Registers in native crashes not ordering numerically; seem to be lexicographic now #76773

Open kpujjigit opened 2 months ago

kpujjigit commented 2 months ago

Description

The general-purpose registers in an ARM crash dump have started using a lexicographic sort and show "r0, r1, r10, r12, r2, r3, ..." instead of being ordered numerically.

When does the problem happen

[ ] During build
[ ] During run-time
[x] When capturing a hard crash

Environment

OS: Linux 4.9

Steps To Reproduce

Crash Occurs and is sent into Sentry, the following is viewed via issue stream:

kahest commented 2 months ago

Seems like it has been like this for a while (see screenshot, PR itself is not directly related) - we probably need to update the sorting here. @priscilawebdev is this something you could take a look at?

getsantry[bot] commented 2 months ago

Routing to @getsentry/product-owners-issues for triage ⏲️

getsantry[bot] commented 2 months ago

Assigning to @getsentry/support for routing ⏲️