Some address in some undefined application, probably not going to get much help with that.
A lot of ST's code has asserts with __LINE__ and __FILE__ references so you don't need source in hand, and someone can look it up. This sort of thing, and hard fault dumps are the sort of thing end-users can push back on developers to help diagnose failure modes/paths.
The binary might contain other strings that would shed some context on the code, sources, and functions surrounding it. A .ELF or .MAP would typically provide symbolic information, narrowing down addresses.
Here, at least you could probably break-point and look at MCU registers and disassembly.
A full disassembly could probably get a good lay-of-the-land.
