Co-routines?
Co-routines?
Posted Jul 14, 2025 14:22 UTC (Mon) by willy (subscriber, #9762)In reply to: Co-routines? by jreiser
Parent article: SFrame-based stack unwinding for the kernel
What would you want a "stack trace" to say for coroutines? They may have called each other millions of times by the time we try to "inspect the stack". Surely you wouldn't want to have millions of repetitions of "producer called consumer called producer called ...". Isn't it enough to know "thread is in producer which was called from event loop"?
Is there any prior work in this area we can steal^W benefit from?
Posted Jul 14, 2025 21:40 UTC (Mon)
by Cyberax (✭ supporter ✭, #52523)
[Link]
Not really. In particular, this makes debugging the coroutine-heavy code a pure nightmare. Debugger becomes worse than useless.
What I'd love is to have a weak link to the "caller frame". It's OK for it to be garbage-collected if the chain becomes too long.
Co-routines?
> Isn't it enough to know "thread is in producer which was called from event loop"?