Boost C++ Libraries: Ticket #3363: linking 2 files compiled with different NDEBUG causes segfault

smr@… — Mon, 04 Jan 2010 02:38:27 GMT

I reproduced this bug with Boost 1.41.

attachment set

smr@… — Mon, 04 Jan 2010 02:40:07 GMT

attachment → valgrid.log

Log of valgrind run with Boost 1.41 on Debian x86_64

attachment set

smr@… — Sun, 28 Feb 2010 04:09:58 GMT

attachment → boost-1.42-valgrind.log

Log of valgrind run with Boost 1.42 on Debian x86_64

Vladimir Prus — Sat, 27 Mar 2010 07:11:22 GMT

Generally speaking, why is this a problem? In general, NDEBUG may change ABI, and therefore should be consistent for entire application -- unless there's a standard saying otherwise.

anonymous — Thu, 01 Apr 2010 02:34:24 GMT

Replying to vladimir_prus:

Generally speaking, why is this a problem? In general, NDEBUG may change ABI, and therefore should be consistent for entire application -- unless there's a standard saying otherwise.

What I can find on the web is http://www.visualco.de/NDEBUG.html which asserts that

The C standard only dictates that when NDEBUG is defined, the assert macro shall expand to nothing. NDEBUG has no other effect or meaning.

The standardization of assert() supports that; c.f. http://www.opengroup.org/onlinepubs/9699919799/functions/assert.html I don't know of anything that states NDEBUG may change ABI -- do you?

One problem the current situation causes is that a boost-using library may be compiled without NDEBUG while someone's application uses NDEBUG, and then goes kabloom when it runs.

smr@… — Mon, 21 Feb 2011 04:29:58 GMT

Hi,

I don't see any activity on this bug, but I just tried it with the 1.46 Release Candidate and the specific issue here seems resolved. I no longer get a segfault.