I've found that: - recompiling openjade on Debian nowadays makes it exhibit the same behavior - recompiling openjade in Debian&Ubuntu with gcc-9 also fails the same way
I'd love to find the root cause, but my hope of identifying either a compiler-default-option or compiler-version that made it break failed. It stays as it was before, you better not recompile openjade otherwise you'll need -O0 or find the yet unknown root cause. IMHO for mostly a doc conversion tool (that also seems mostly dead upstream) speed isn't super-important and while not perfect -O0 should be ok'ish for the time being. For now the mitigation worked, pgpool2 for example now built fine: https://launchpad.net/ubuntu/+source/pgpool2/4.1.4-2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to openjade in Ubuntu. https://bugs.launchpad.net/bugs/1869734 Title: openjade segfaults on arm (due to gcc optimization) Status in openjade package in Ubuntu: Triaged Status in pgpool2 package in Ubuntu: New Bug description: <Myon> cpaelzer: fun, openjade segfaulting on focal/arm64 <cpaelzer> I beg your pardon for my ignorance of the ecosystem, but how is this related to postgresql-apt <cpaelzer> for doc generation? <Myon> cpaelzer: the postgresql-9.5 and -9.6 builds fail during doc generation on focal/arm64 <Myon> everything else (other archs, other dists) is fine <Myon> https://pgdgbuild.dus.dg-i.net/job/postgresql-9.5-binaries/architecture=arm64,distribution=focal/55/console <cpaelzer> Myon: only on arm64? <Myon> only there, yes <Myon> ./configure && make -C doc/src/sgml all should reproduce it <cpaelzer> clone and build this branch ? https://github.com/postgres/postgres/tree/REL9_5_STABLE <Myon> the crash is in /usr/lib/libostyle.so.1 from libostyle1c2 <cpaelzer> here it is <cpaelzer> segfault <Myon> I have this now http://paste.debian.net/1136839/ <cpaelzer> https://paste.ubuntu.com/p/CfzrfWkqzs/ <cpaelzer> well I wanted to get -O0 to see more int he debugger <cpaelzer> my build worked as well now <Myon> the -O0 openjade installed doesn't segfault <cpaelzer> oh so like my -O0 then <cpaelzer> so maybe we should just always -O0 openjade then? <cpaelzer> TBH who cares about optimization in that <cpaelzer> But its usage is mostly build time and not runtime <Myon> maybe -O0 on arm64 only <cpaelzer> I'm rebulding -O2 again to recheck if that really is it <cpaelzer> and then -O1 to check the in between <cpaelzer> it might "just" need a rebuild <cpaelzer> -O2 re-build segfault <cpaelzer> -O1 (for completeness) rebuild ... seems to hang? <Myon> probably not really relevant <cpaelzer> agreed, but I want to rebuild -O0 again just to see it builds and then works <cpaelzer> -O0 on arm64 really seems to be a good choice <Myon> I can try if rebuilding makes it fail on sid <Myon> cpaelzer: recompiling openjade in arm64/sid doesn't make it segfault <Myon> so it seems this needs a focal-only fix <Myon> cpaelzer: the openjade segfault is also present in pgpool2, so not just in ancient PostgreSQL :( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjade/+bug/1869734/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
