_stackTrace is pointing incorrectly in Unity when clicked on Exceptions

[JohanHoltby]

Hi All!
Please inform me if I'm missing some standard info or format!

I'm building a new Unity play mode testing framework which will support UniTask as they are awsome. One problem however is that when the assertions are thrown and I catch them in the test runner the _stackTrace (with the pointers) seams to be missing the pointer to the test code.

Any how when I then do Debug.LogException(e) and click on the exception in unity the Raider IDE takes me to the point where Debug.LogException(e) was logged not as with normal tasks which runs pretty much the same code correctly takes the user to the actual assertion.

Is this a error on my behalf on how i catch and log the exception?
If I log the exception in the UniTask then still it points to the Debug.LogException(e).

It would be more convinient if UniTask would work as Task.

I'm willing to contribute but wanted to lift this as Issue first and if you agree I could dig in to it and implement a fix in UniTask,

[SulfuricAcidH2SO4]

In unity, if you click on an exception in the lower half of the console you can see the entire stack trace, on the second line you get line that threw the exception highlighted in blue. You can just click on that and it will jump you to the correct line.