--- Please enter the report below this line. ---
Dear Maintainer,

  By default context boost uses fcontext_t, which makes address & thread
sanitizers unusable (strangely thread sanitizers used to work with boost 1.62,
but with 1.67 are unusable).
  It will be great if debian provides also an ucontext_t alternative build
(libboost-ucontext-dev ?) which replaces fcontext_t and enables the usage of
address & thread sanitizers.

For more informations check:
https://github.com/boostorg/coroutine2/issues/12
https://github.com/boostorg/coroutine/issues/30
https://www.boost.org/doc/libs/1_67_0/libs/context/doc/html/context/cc/
implementations__fcontext_t__ucontext_t_and_winfiber.html

Thanks!

--- Package information. ---
Depends                       (Version) | Installed
=======================================-+-===========
libboost-context1.67-dev                | 1.67.0-10

Hi,

Il 21/11/18 14:53, Bogdan Vatra ha scritto:

I tend to agree this might be useful, also to provide an implementation
of context on architectures not supported by fcontext_t. But also keep
in mind that ucontext_t is much slower.

Also, it must be checked that this does not introduce other kind of
problems that could slow the release, and on top of that I am not sure I
will have the time to work on that.

Giovanni.

Dear maintainer,

I've prepared an NMU for boost1.90 (versioned as 1.90.0-6.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I should
cancel it.

   * Enable context everywhere. (Closes: #914283)
   * Build with address-model=$(DEB_TARGET_ARCH_BITS). (Closes: #1130963)
   * Stop disabling pch on arm64.
   * Disable numpy on x32 until it is available again.
   * Fix the autopkgtest for GCC 16.
   * Fix and re-enable the graph autopkgtest.
   * Remove remnants of the removed system autopkgtest.
   * Improve reproducibility.

cu
Adrian

We believe that the bug you reported is fixed in the latest version of
boost1.90, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 914283@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk <bunk@debian.org> (supplier of updated boost1.90 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Sun, 09 Aug 2026 21:10:47 +0300
Source: boost1.90
Architecture: source
Version: 1.90.0-6.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Boost Team <team+boost@tracker.debian.org>
Changed-By: Adrian Bunk <bunk@debian.org>
Closes: 914283 1130963
Changes:
 boost1.90 (1.90.0-6.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Enable context everywhere. (Closes: #914283)
   * Build with address-model=$(DEB_TARGET_ARCH_BITS). (Closes: #1130963)
   * Stop disabling pch on arm64.
   * Disable numpy on x32 until it is available again.
   * Fix the autopkgtest for GCC 16.
   * Fix and re-enable the graph autopkgtest.
   * Remove remnants of the removed system autopkgtest.
   * Improve reproducibility.
Checksums-Sha1:
 6ae8ac8d5ad879ebbfe1284e67a31d1e5352a786 8383 boost1.90_1.90.0-6.1.dsc
 081b0a31005b1b0399541fc5ee8fa45f0950f4d8 372300 boost1.90_1.90.0-6.1.debian.tar.xz
Checksums-Sha256:
 596e32ba7037f68287368dc31486b6414c59f6de71c1f04479e5a857ebc9d93c 8383 boost1.90_1.90.0-6.1.dsc
 ce301722034d9db70987d3f876ad670bda7581957e8842907d401078411f7af6 372300 boost1.90_1.90.0-6.1.debian.tar.xz
Files:
 a62dfaa05a0891ccfa8265523a5a5ca7 8383 libs optional boost1.90_1.90.0-6.1.dsc
 10d6d5c2265b1abc56a5b0256d93ebfb 372300 libs optional boost1.90_1.90.0-6.1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmp4/KAACgkQiNJCh6LY
mLEXjxAAy9ltAZiBkSfIrJO5+F/ghx8/dmUw52fsLYHxM0Mo9z600rX+/QKNogWJ
dUFRsWs5noktd3lpR0Dh0Lm49SLrg7Kb6RIc9TjM8as79VevSmOhrsw50p20PgxZ
oWc0XYSsfuVSJI+bNatZeJl2R+6fVdL/8LuNwNoXhYbSftZj850GprdZCcQkFuQ/
ByVPorzXqPd76qAJMZJfGW27FCGDv1N8M6gTdd7RO+fN08viNJi7vSv9fJ7xPrpk
ufJCQfe9tS6+CWvVprnxRZWFI9eKSJ6ErE4Jszq8bSimjlPkHFl3SyugFg1UDGDd
LgZCXAtOdPvSkXzLwc8q4AFKR3adrQNXPU/BYLxpnbDzANxqVLWCZzNycPCP5rzq
EEkR34BftE671DvorK97MdqI3qYmqN104NE+MO7kDJJR6d5kD/K/s8ZkQbG/+XJ/
62AgqZP3/xllLnNnBz7ITp6qPOur+OMfaAJz1AxxApZ2qHCPxBg+dI7c1CIpxnhD
Z2zWt44RBz21rbN8f3ICfb1lIezxoxtirhEWylOsKR7rg8sbucPPAGszu7nOPz6R
NzIfqRxAWfhK10j89RDshNkzsgajaE3hrsUh30rfOaup1EDIhSz36NAuqCixnTbo
3S/HaiMOpMNlVgpZ1/3YjDI0r+YA7tj7f5Uop5I3/M44qLoyaAk=
=cC4H
-----END PGP SIGNATURE-----

Hi!

This one caught my eye, as using DEB_TARGET_* is usually suspect.
Is this really intended for Canadian cross-compiler support? Or should it
be instead DEB_HOST_ARCH_BITS?

While at it, this also seemed suspect. Is this really for the build
system instead of the host one?

Thanks,
Guillem

Hi!

I actually thought about that one before doing it, and I did not see a
difference between host and target in that case so that's rather random.

Good catch.

That was me modifying an old option instead of writing it from scratch,
and not looking closely what it was.

cu
Adrian