Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cleanup stacktraces to not contain intrinsic method calls #3456

Conversation

WojciechMazur
Copy link
Contributor

Before:

java.lang.RuntimeException
        at java.lang.StackTrace$.currentStackTrace$$anonfun$1(Throwables.scala:57)
        at java.lang.StackTrace$$$Lambda$3.applyVoid(Throwables.scala:87)
        at scala.runtime.function.JProcedure1.apply(JProcedure.scala:28)
        at scala.scalanative.unsafe.Zone$.apply(Zone.scala:29)
        at java.lang.StackTrace$.currentStackTrace(Throwables.scala:50)
        at java.lang.Throwable.fillInStackTrace(Throwables.scala:146)
        at Test$.main(Test.scala:3)
        at Test.main(Test.scala:3)
        at <none>.main(unknown:2)

After:

java.lang.RuntimeException
        at Test$.main(Test.scala:3)
        at Test.main(Test.scala:3)
        at <none>.main(unknown:2)

@WojciechMazur WojciechMazur force-pushed the stactraces/cleanup-internal-frames branch from ed67654 to 8dc83f4 Compare August 26, 2023 03:49
…e used for currentStackTrace recursion detection. Threads created by Thread.Builder might not have access to ThreadLocal values.
@WojciechMazur WojciechMazur merged commit b88b1d4 into scala-native:main Aug 27, 2023
79 checks passed
@WojciechMazur WojciechMazur deleted the stactraces/cleanup-internal-frames branch August 27, 2023 12:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant