Bug#1104044: orthanc-wsi: Plugin OrthancWSI fails to start on arm64, ppc64el, riscv64 and s390x

Étienne Mollier <[email protected]> Thu, 24 Apr 2025 22:47:52 +0200

Newsgroups	gmane.linux.debian.ports.s390
Message-ID	<aAqjeBWscODFiB4c__37045.5210375198$1745527899$gmane$org@emlwks999.eu>

Package: orthanc-wsi
Version: 3.2+dfsg-4
Severity: serious
Justification: autopkgtest failure
X-Debbugs-Cc: [email protected], [email protected], [email protected], [email protected]
User: [email protected]
Usertags: s390x
User: [email protected]
Usertags: arm64
User: [email protected]
Usertags: ppc64el
User: [email protected]
Usertags: riscv64

Hi Sébastien,

We're almost there with getting dcmtk and the Orthanc ecosystem
to migrate to trixie.  The remaining issues[1] only affect
orthanc-wsi, and on a particular set of CPU architectures
(arm64, riscv64, ppc64el and s390x).

[1]: https://qa.debian.org/excuses.php?package=dcmtk

Upon analysis, it looks like the root cause of the crash in
autopkgtest can be reproduced on affected architectures by
running:

	# Orthanc --verbose /etc/orthanc/
	[…]
	E0424 18:38:19.841699             MAIN wsi:/Plugin.cpp:492] Exception in startup tests: Internal error

Given that the raising of this error is most likely provoked by
a computational error, and given the set of architectures
affected by the regression, I hoped that the resolution could be
a simple matter of enforcing signed char at build time.  However
my attempts at enforcing char signedness with -fsigned-char were
inefficient in resolving the crash, which suggests the issue may
be more intricate than I think.

Per chance, do you have an idea what the root cause would be?

If not, then in order to facilitate dcmtk transition, I plan to
disable affected architecture in autopkgtest control file, and
reduce the severity of the present bug to important.

Thank you for your help this far,  :)
-- 
  .''`.  Étienne Mollier <[email protected]>
 : :' :  pgp: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/1, please excuse my verbosity
   `-

signature.asc (application/pgp-signature, 833 B)