Date: Wed, 19 Nov 2025 02:45:33 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 291091] WITH_ZEROREGS breaks python interpreter Message-ID: <bug-291091-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291091 Bug ID: 291091 Summary: WITH_ZEROREGS breaks python interpreter Product: Base System Version: 15.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: misc Assignee: bugs@FreeBSD.org Reporter: andreas@turriff.net I am uncertain whether this bug belongs here, under Ports, or should properly be reported to Python upstream; I am filing it here as the immediate symptom originates with the base system. An experimental build of FreeBSD 15.0-BETA5 (and reproduced on -RC2) with WITH_ZEROREGS=yes led to some interesting behavior in my installed CPython interpreters, both from Ports and managed by pyenv. Specifically, return values from calls into the C library moderated by the "ctypes" module in Python suddenly started returning 0 instead of the expected retval. To me, this was particularly notable as setfstab() suddenly returned 0, breaking sysutils/iocage in the process. Further investigation revealed that this behavior vanishes and return values are as expected when deploying, without further changes, a base system built without WITH_ZEROREGS in src.conf. This may well be a case of "if it hurts, don't do it," but it's (mis)-behavior I'd like to see fixed. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-291091-227>