FS#71673 - [meson] Consider adding -Db_ndebug=true to arch-meson

Attached to Project: Arch Linux
Opened by Jan (medhefgo) - Saturday, 31 July 2021, 13:01 GMT
Last edited by Toolybird (Toolybird) - Monday, 25 September 2023, 04:10 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Levente Polyak (anthraxx)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Without -Db_ndebug=true or -Db_ndebug=if-release, many meson projects are build without NDEBUG, which results in assert() getting into production/release builds.
This task depends upon

Closed by  Toolybird (Toolybird)
Monday, 25 September 2023, 04:10 GMT
Reason for closing:  Won't fix
Additional comments about closing:  See comments from PM. Also, to address 1 of the comments, Arch now does provide debug pkgs.
Comment by Jan Alexander Steffens (heftig) - Sunday, 01 August 2021, 17:13 GMT
I think this is something that needs to be handled per-project.
Comment by Michel Koss (MichelKoss1) - Sunday, 08 August 2021, 14:21 GMT
Isn't it a bit if burden having every package that uses meson disabling asserts themselves? This is like arch didn't provided any buildflags but every package needed to pass -O2... etc.

arch-meson adverts itself as "Highly opinionated wrapper for Arch Linux packaging". Currently it enables features like lto but can't disable asserts in release builds? Why is that?

BTW: meson has b_ndebug=if-release which I think would suit better.
Comment by Jan Alexander Steffens (heftig) - Sunday, 08 August 2021, 14:25 GMT
Why should asserts be disabled at all? Some projects expect distribution packages to have them.
Comment by Michel Koss (MichelKoss1) - Sunday, 08 August 2021, 14:37 GMT
Asserts are in essence debugging feature that make it easier to catch bugs while testing code. Most often catching such bug with asserts enabled leads to crash while otherwise it may be note observable by end user with asserts disabled. I believe most arch users didn't sign up for being code testers especially when arch doesn't provide any debug code info which makes reporting such bugs to upstream very hard if not impossible.
Comment by Jan (medhefgo) - Monday, 09 August 2021, 14:56 GMT
Thinking about this more, it certainly makes sense to have asserts in production builds for many projects. Whichever default is picked, I feel like making it explicit in arch-meson along with a comment sounds like a good idea.
Comment by Buggy McBugFace (bugbot) - Tuesday, 08 August 2023, 19:11 GMT
This is an automated comment as this bug is open for more then 2 years. Please reply if you still experience this bug otherwise this issue will be closed after 1 month.

Loading...