id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
3363	linking 2 files compiled with different NDEBUG causes segfault	smr@…	az_sw_dude	"Linking y1.o and y2.o compiled as below causes the resulting executable to segfault and show valgrind errors.
x1.o defines NDEBUG before including a boost header, x2.o doesn't.
If both define NDEBUG, or both don't then linking them produces an executable that runs, and shows no valgrind errors.

This is y1.cpp:
#define NDEBUG 1
#include <boost/date_time/posix_time/posix_time.hpp>
#include <iostream>

void foobar() {
    boost::posix_time::time_duration td(0, 0, 1, 0);
    std::stringstream ss;
    ss << td;
}
void bar(void);
int main()
{
    bar();
    return 0;
}

This is y2.cpp:
#include <boost/date_time/posix_time/posix_time.hpp>
void bar(void) {
    std::cerr<<boost::posix_time::second_clock::local_time()<<' ';
}

Fails:
$ g++ y1.cpp y2.cpp && ./a.out
Segmentation fault

Reported by Debian user; see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537680 for valgrind output.

I have reproduced this behaviour on today's trunk, so I expect it is still a problem in 1.39.0 and upcoming 1.40.0.


"	Bugs	new	Boost 1.40.0	date_time	Boost 1.39.0	Problem