Investigate why StackFrameHelperTest Trimming test fails on mono

[joperezr]

PR #48429 added the browser-wasm leg to our Trimming tests and this was the first time that our trimming tests would run against the mono runtime. One of the findings when analyzing the results was that the test StackFrameHelperTest was failing due to the fact that it wasn't able to retrieve the line information from a newly created StackTrace object. The test was disabled on that same PR due to the fact that the test's intention was actually to validate that a linker annotation was preserving the right methods in order for line information to be retrieved correctly, and this annotation was specific to coreclr's runtime, so it didn't make sense to run it on Mono. That said, we should take a look and see why line information isn't able to be retrieved when running on Mono in case this is not a known issue or by design.

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[ghost]

Tagging subscribers to this area: @tarekgh, @tommcdon, @pjanotti
See info in area-owners.md if you want to be subscribed.

Issue Details

---

PR #48429 added the browser-wasm leg to our Trimming tests and this was the first time that our trimming tests would run against the mono runtime. One of the findings when analyzing the results was that the test StackFrameHelperTest was failing due to the fact that it wasn't able to retrieve the line information from a newly created StackTrace object. The test was disabled on that same PR due to the fact that the test's intention was actually to validate that a linker annotation was preserving the right methods in order for line information to be retrieved correctly, and this annotation was specific to coreclr's runtime, so it didn't make sense to run it on Mono. That said, we should take a look and see why line information isn't able to be retrieved when running on Mono in case this is not a known issue or by design.

Author:	joperezr
Assignees:	-
Labels:	area-System.Diagnostics.Tracing, runtime-mono
Milestone:	-

[joperezr]

FYI: @marek-safar

[ghost]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

PR #48429 added the browser-wasm leg to our Trimming tests and this was the first time that our trimming tests would run against the mono runtime. One of the findings when analyzing the results was that the test StackFrameHelperTest was failing due to the fact that it wasn't able to retrieve the line information from a newly created StackTrace object. The test was disabled on that same PR due to the fact that the test's intention was actually to validate that a linker annotation was preserving the right methods in order for line information to be retrieved correctly, and this annotation was specific to coreclr's runtime, so it didn't make sense to run it on Mono. That said, we should take a look and see why line information isn't able to be retrieved when running on Mono in case this is not a known issue or by design.

Author:	joperezr
Assignees:	-
Labels:	arch-wasm, area-System.Runtime, runtime-mono
Milestone:	-

[dakersnar]

Is this the correct area label for this issue?

[tommcdon]

This is an older issue, and we have had no known customer issues raised because of it. Closing until we have more feedback.