Post #2637534
2026-02-17 12:01 UTC
@cocoafrog@hachyderm.io @ktoso@mastodon.social @ole@chaos.social but it won’t show me what line of code each task is currently at the way I can with threads.
It’s also very difficult for me to profile tests, because our tests rely on some hooks we only allow in DEBUG and I’ve had a very hard time getting SwiftPM packages to be profiled in DEBUG, or to pass a flag we could use instead. (Making that work is a big goal for this year.)
Problem is also not consistent and may be a test order interaction, which is hard with Instruments.
Replies (1)
-
@ktoso@mastodon.social 2026-02-17 12:40
@cocoaphony@mastodon.social @cocoafrog@hachyderm.io @ole@chaos.social hm… the “where is the task” is pretty difficult to answer… might need some lldb experts to see if it’s feasible to connect continuations to source locations somehow in post processing hm