When debug files are found in the symbol server, but don't contain debug metadata in them. The UI should be more indicative:
@tobias-wilfert indicated having the indication on the frame itself would be more helpful to have an indication on the frame itself so it's more clear that something is wrong.
Personally would feel like just having some indication on the stacktrace might be more helpful (than changing the colour) :thinking_face: since I for example did not know that you can click on the blue address and it takes you to the file description in the above image. (Tooltip and link to documentation sound nice though).
Alternatively, and an easy win might be to show that greyed out part in red:
With a tooltip indicating what this is about. What data that is, and how to include that when compiling the code.
These details should be on a page in the docs, and the tool tip should point to it.
e.g:
If you use clang here’s how u compile with debug info, etc
When debug files are found in the symbol server, but don't contain
debug
metadata in them. The UI should be more indicative:@tobias-wilfert indicated having the indication on the frame itself would be more helpful to have an indication on the frame itself so it's more clear that something is wrong.
Alternatively, and an easy win might be to show that greyed out part in
red
:With a tooltip indicating what this is about. What data that is, and how to include that when compiling the code. These details should be on a page in the docs, and the tool tip should point to it. e.g: