Raygun Feature Request

Raygun currently has the ability to upload:

• Debugging symbol files for C/C++ applications (https://raygun.com/documentation/language-guides/cpp/crash-reporting/installation/)
• Minidump files when errors/crashes occur (such as those generated by Breakpad)

However, in the Raygun Dashboard, the results reported in each individual crash/error instance are very limited and show (machine readable) memory addresses in library files rather than human-readable line numbers in function names. Below is the example output from the Raygun provided sample C++ application:

In the case of C applications, the results are even more limited (no class names etc are shown - just library name and memory offset/address). In my specific case, my entire stack traces look similar to lines 1 and 2 of the stack trace above.

For most cases, the machine readable data would be the bare minimum required to debug an application, but it's very cumbersome and time consuming to convert the memory addresses to line numbers.

It's also very error-prone as the memory addresses are specific to the version of the library/code at the time of the error report. So looking back at old errors involves downloading old versions of the code, making the process even more difficult.

I'd like to request some more development in debugging these C/C++ applications by providing human-readable stack traces in Raygun Dashboard.