Oliver Kowalke

Results 59 comments of Oliver Kowalke

Segfault with ucontext on macOS (#184, continued)

Could you check if this issue is solved by #236 (branch develop)?! I can't do it because I don't own a MAC system.

Segfault with ucontext on macOS (#184, continued)

seams to be an issue of defining _XOPEN_SOURCE in fiber.hpp

Coroutine does not build cleanly on OS-X in universal mode (arm+x86)

Sorry - I've no access to an machine with OS-X...

Coroutine does not build cleanly on OS-X in universal mode (arm+x86)

The arm64 assembler tool doesn't find symbol _jump_fcontext which is the label/function name of jump functionality. I don't know the requirements for labels in the universal mode on OS-X.

Coroutine does not build cleanly on OS-X in universal mode (arm+x86)

relates to https://github.com/boostorg/context/issues/203

Coroutine does not build cleanly on OS-X in universal mode (arm+x86)

Sorry, I need to debug the code but unfortunately I have no OSX ... maybe this issue of boost.context https://github.com/boostorg/context/issues/214 fixes your problem?

Tasks with 'none_failed_min_one_success' trigger_rule skipping before Dynamic Task Group is fully expanded

I observe a similar behavior in 2.10.4. I filled in a bug report that was unfortunately moved to 'discussion' - #46315. The solution I found was to pass the task...

Tasks with 'none_failed_min_one_success' trigger_rule skipping before Dynamic Task Group is fully expanded

OK, unfortunately I've the impression that nobody takes care about 'discussions' - anyway the 'issue' seams already be addressed in another bug ticket (I've linked each other).

MASM : fatal error A1013:invalid numerical command-line argument : /W

PR #294 merged

add an ability to execute a callback function on behalf of target coroutine stack right before return to target coroutine

executing a function before resuming a coroutine is done via ontop_fcontext() - wouldn't this satisfy your needs?