GDB stack trace is incomplete when enabling Perf support under specific optimization options on x86_64. It seems that through various changes the stack trace was broken and/or fixed.

This comes from the tracing code’s Scope.reset_current_trace (token) call in Trace.finish (), because the token was set in the parent task’s context but is being reset in the spawned Task’s context.