Hi,
You say yourself that a simple test program succeeds. The bug materializes only in your production code. This scenario begs for the steps for reproduce the bug. If you cannot reproduce it then you shouldn't suggest that it's a bug in boost. If the same code succeeds in a simple test program then it cannot be a bug in boost IMHO.
Unfortunately, we had this exact case 2 days ago with a spirit::qi bug, induced by an uninitalised variable and a weird edge case. But i would agree that confirmation of this can only be given by a proper valgrind run( or a similar tool) to record any weird memory issues. If the testprogram succeeds without valgrind finding anything, do the same with your full program. compile in debug and run valgrind. Best, Oswin