Resources are set as unknown during measurement on some DWARF labels

[markhakansson]

Expected behavior

When measuring Rauk should correctly try to find the names of the resources used in resource locks. At least on debug.

Actual behavior

When some resources are labeled with DW_AT_ranges instead of DW_AT_low_pc & DW_AT_high_pc it will be ignored and the name of the resource will be set to <UNKNOWN>.

Steps to reproduce

1. Do the same resource locks multiple times in a task (e.g. a.lock() then a.lock() again)
2. Run all Rauk steps

Additional context

[markhakansson]

Support for DW_AT_ranges does not completely fix this issue. Happens for other things as well. Not sure what the cause is yet.

[markhakansson]

It might be because of https://docs.rust-embedded.org/book/static-guarantees/zero-cost-abstractions.html