Thread overview
[Issue 16106] Calling a fiber from itself causes hard-to-debug stack corruption
May 31, 2016
Don
Jul 02, 2017
Vladimir Panteleev
Dec 17, 2022
Iain Buclaw
May 31, 2016
https://issues.dlang.org/show_bug.cgi?id=16106

--- Comment #1 from Don <clugdbug@yahoo.com.au> ---
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.

Ie, fiber.call() should either switch to a different fiber, or else it should halt execution. It should never cause stack corruption.

--
July 02, 2017
https://issues.dlang.org/show_bug.cgi?id=16106

--- Comment #2 from Vladimir Panteleev <dlang-bugzilla@thecybershadow.net> ---
A minimal test case exhibiting the problem would be nice!

--
December 17, 2022
https://issues.dlang.org/show_bug.cgi?id=16106

Iain Buclaw <ibuclaw@gdcproject.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P1                          |P4

--
December 07
https://issues.dlang.org/show_bug.cgi?id=16106

--- Comment #3 from dlangBugzillaToGithub <robert.schadek@posteo.de> ---
THIS ISSUE HAS BEEN MOVED TO GITHUB

https://github.com/dlang/dmd/issues/17329

DO NOT COMMENT HERE ANYMORE, NOBODY WILL SEE IT, THIS ISSUE HAS BEEN MOVED TO GITHUB

--