Hi Riccardo, Riccardo Mottola via pkg-GNUstep-maintainers wrote: > is the issue reproducible on a system you have on where you can get a > stacktrace?
I already asked Paul for a backtrace (see https://bugs.debian.org/1087735). > I just tested on my Linux i386 laptop running Devuan with GCC runtime > (all source being GIT and compiled by myself, no packages) and I have > no issues with GWorkspace. FWIW, I also cannot reproduce on i386, but this is on a bookworm machine with manually built latest GNUstep + GWorkspace from tarballs; GCC 12.2.0. The OP reports the bug on trixie, GCC 14.2.0. > Thus we must understand what is happening at your place. Certainly. > First thing I see is that the screenshot shows a different exception > than the one you describe. NSConstantString vs NSImage. I also noticed this. > We need to know how gnustep core and gworkspace is compiled. To answer your questions: gnustep-base is confugured with --disable-bfd; gnustep-gui with --disable-icu-config --enable-imagemagick. The compiler options used (in addition to those defined by gnustep-make) are: $ dpkg-buildflags --get CPPFLAGS -Wdate-time -D_FORTIFY_SOURCE=2 $ dpkg-buildflags --get OBJCFLAGS -g -O2 -ffile-prefix-map=/<path>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection The full build log is available here: https://buildd.debian.org/status/fetch.php?pkg=gworkspace&arch=i386&ver=1.0.0-4&stamp=1727349221&raw=0 > Do you have PDFKit installed and is it enabled? No; we can't have PDFKit in Debian. The Debian gworkspace package uses PopplerKit and it's the only patch to the pristine upstream source: https://sources.debian.org/src/gworkspace/1.0.0-4/debian/patches/popplerkit.patch/ > did you enable GWMetadata? Yes; the package is configured with --enable-gwmetadata --with-sh=/bin/sh --with-unzip=unzip.
