Package: openjade Version: 1.4devel1-21.3+b1 Hi, you are not "yet" affected by this, but tests in debian-unstable have shown that you will be affected as soon as anyone re-builds openjade as it is today.
What happened is that in Ubuntu first only on arm64 later on all architectures openjade segfaulted. That happened in various cases e.g. postgresql-13 or pgpool2 builds, see [2] for details. Repro: # enable sources for apt $ apt upgrade $ apt install dpkg-dev openjade docbook-dsssl $ apt source pgpool2 $ cd pgpool2-4.1.1/doc/src/sgml/ $ openjade -wall -wno-unused-param -wno-empty -wfully-tagged -c /usr/share/sgml/docbook/stylesheet/dsssl/modular/catalog -d stylesheet.dsl -t sgml -i output-html -V html-index pgpool.sgml Build openjade from the very same source: $ apt build-dep openjade $ apt source openjade $ cd openjade-1.4devel1 $ ./debian/rules build Then test with this path to the binary-wrapper /root/openjade-1.4devel1/jade/openjade, that will deliver the same segfault we see in Ubuntu: $ /root/openjade-1.4devel1/jade/openjade -wall -wno-unused-param -wno-empty -wfully-tagged -c /usr/share/sgml/docbook/stylesheet/dsssl/modular/catalog -d stylesheet.dsl -t sgml -i output-html -V html-index pgpool.sgml I was unable to find the root cause, but until that is done a working mitigation seems to be to set flags to "-O0". P.S. I'm not entirely convinced this is a Dup on, so I reported a new bug and leave it up to you to merge or not. P.P.S. I have tried building with gcc-9, but it exposes the same segfault - it must be something else than the compiler itself. [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489482 [2]: https://bugs.launchpad.net/ubuntu/+source/openjade/+bug/1869734 -- Christian Ehrhardt Staff Engineer, Ubuntu Server Canonical Ltd
