[Issue 16106] Calling a fiber from itself causes hard-to-debug stack corruption

2022-12-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16106 Iain Buclaw changed: What|Removed |Added Priority|P1 |P4 --

[Issue 16106] Calling a fiber from itself causes hard-to-debug stack corruption

2017-07-01 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16106 --- Comment #2 from Vladimir Panteleev --- A minimal test case exhibiting the problem would be nice! --

[Issue 16106] Calling a fiber from itself causes hard-to-debug stack corruption

2016-05-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16106 --- Comment #1 from Don --- To clarify: I'm asking for the situation where you call a fiber which is not in state HOLD, to be detected even when compiled without contracts. I'm not asking for fiber.call() to ever be a no-op.