Public bug reported:

When stackful coroutines are used with asynchronous operations, and the
completion signature starts with std::exception_ptr, the program is
unexpectedly terminated during a SUCCESS scenario (SIGSEGV).

This was noticed with the ceph package, and detailed here:
https://github.com/canonical/microceph/issues/810

This affects ceph 20.2.x when deployed on noble, which will happen on an
upcoming noble release.

This has been fixed in 1.84, but Noble uses 1.83, and can affect
applications there.

Upstream fix:
https://github.com/boostorg/asio/commit/27c352f77d1806c7eed8ea91def6c4bc5f3715c1

** Affects: boost1.83 (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: ceph (Ubuntu)
     Importance: Undecided
         Status: New

** Also affects: ceph (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2163705

Title:
  spawn-based stackful coroutines terminate programs when used with
  asynchronous operations that have a completion signature starting with
  std::exception_ptr

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/boost1.83/+bug/2163705/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to