Debug sym files can have inline function information. When we update the stackwalker (bug #1779630), then the stackwalker will be outputting inline function information.

This bug covers figuring out what changes we need to make in the Socorro processor and webapp and making them or spinning off new bugs.

It's probably something along the lines of:

1. add the relevant bits to the processed crash schema
2. figure out how to display inline function information in the crashing thread stack in the Crash Stats report view
3. figure out whether we want to factor inline function information into signature generation

See Markus' suggested mockups: https://bugzilla.mozilla.org/show_bug.cgi?id=1398533

I used Markus' patch and did a try build:

https://treeherder.mozilla.org/jobs?repo=try&revision=324e9f44d80b536cd8edf76b5543dc1cc3bdf488&selectedTaskRun=BGjLfXqBRa-siB4RU5VYfg.0

I used that build to create a crash report:

https://crash-stats.mozilla.org/report/index/20aec939-4154-4520-ba3c-024930220902

I'll use that to implement this with.

willkg merged PR #6175: "bug 1788103: show inline functions in details tab of report view" in 590f25b.

This got pushed to prod in bug #1789701. I told Markus about it. He mentioned that when he asked on #crashreporting-wg, people preferred the other mockup.

mstange: when I asked for opinions on this channel, two or three people said the preferred separate rows for each inline, with "trust" set to "inlined"

My minor issue was that I found the frame numbering confusing. Markus suggested this:

mstange: yeah you'd have two different types of frame indexes

"normal frame index" and "frame index after inline expansion"

or you could just repeat the same frame index, I think that would be fine too

I'll fix the implementation to match that.

PR 6181 changes the display to the other mockup. It also fixes the ordering which Nika pointed out was wrong. Now it displays inline functions and then the frame function.

willkg merged PR #6181: "bug 1788103: redo display of inline functions in report view" in 77ce349.

This was deployed in bug #1790053. Marking as FIXED.