Boost C++ Libraries: Ticket #3104: Preprocessing with Boost::wave crashes when calling from multiple threads

attachment set

www.brutaltruth.ru — Thu, 28 May 2009 09:10:30 GMT

attachment → wave_bug_MT.zip

MSVS2008 project

status changed; resolution set

Hartmut Kaiser — Thu, 28 May 2009 15:03:23 GMT

status new → closed
resolution → fixed

Thanks for this report. It has been fixed recently and the patch will be part of Boost V1.40.0.

Regards Hartmut

anonymous — Fri, 29 May 2009 10:13:21 GMT

Replying to hkaiser:

Thanks for this report. It has been fixed recently and the patch will be part of Boost V1.40.0.

Regards Hartmut

I have tested again with boost trunk and the problem is still there. Wave changelog lists 2 "race conditions" fixed. Is it related to this bug or the changes are not in the trunk yet?

anonymous — Sat, 30 May 2009 15:35:46 GMT

The problem with your code is that you are including the Spirit headers files independently and before including Wave. Wave enables Spirit thread safety whenever it is compiled in multi-threaded mode. But if you include Spirit before Wave you need to switch Spirit (and probably Phoenix) into multi-threaded mode yourself. I was able to run your example successfully by adding:

#define BOOST_SPIRIT_THREADSAFE 1
#define PHOENIX_THREADSAFE 1      // needed only if you use Phoenix

to your stdafx.h before including Spirit.

HTH Regards Hartmut

www.brutaltruth.ru — Mon, 01 Jun 2009 07:22:28 GMT

Thank you, Hartmut!

www.brutaltruth.ru — Mon, 01 Jun 2009 08:45:27 GMT

Hartmut, i have tested my sample with defines that you suggested - it still causes Heap corruption problems (but no problems with asserts as sometimes before). Actually sample i attached for you is OK - there are only couple of little files used to be precompiled. As i add more files to precompile - heap corruption dialog pops back again. I am sorry for annoying you, just want Wave to be ok in next boost release.

Hartmut Kaiser — Mon, 01 Jun 2009 13:04:26 GMT

Replying to www.brutaltruth.ru:

Hartmut, i have tested my sample with defines that you suggested - it still causes Heap corruption problems (but no problems with asserts as sometimes before). Actually sample i attached for you is OK - there are only couple of little files used to be precompiled. As i add more files to precompile - heap corruption dialog pops back again.

Could you provide a minimal example I could use to reproduce your problem?

I am sorry for annoying you, just want Wave to be ok in next boost release.

No annoyance at all. I appreciate you patience.

Regards Hartmut

tony — Tue, 02 Jun 2009 14:52:02 GMT

Thank you, Hartmut. Just compile the sample i sent you in Release settings and run it several times (3 or 4 and Heap corruption pops). Good bye.

Hartmut Kaiser — Thu, 04 Jun 2009 14:34:18 GMT

Replying to tony :

Just compile the sample i sent you in Release settings and run it several times (3 or 4 and Heap corruption pops).

I'm sorry, but I'm not able to reproduce your problems even when running in release mode a couple of times (I set up an endless loop executing your example and it ran for over an hour just fine). Any other idea how I could reproduce this effect?

Regards Hartmut