Hi, Has any one else had a *glibc error (invalid free/delete issue)* pointing to boost_program-options in boost 1.39.0? Program exits with glibc error (double free; although nothing obvious stands out). Running valgrind hasn't really helped a lot. Is this a known boost issue in 1.39.0? I am using non-multithreaded versions of the boost libs: program-options, regex, iostreams, python, filesystem, system, date_time, unit_test_framework, and multithreaded version only for boost lib: thread. I've reached my wit's end on this problem that occurs only on linux (red hat 5, GNU compilers, GCC version 4.1.2) and any advice is helpful. Greatly appreciate if you could share your experience on how you fixed it. Thanks! --Tom.
Sunil Thomas wrote:
Hi,
Has any one else had a *glibc error (invalid free/delete issue)* pointing to boost_program-options in boost 1.39.0? Program exits with glibc error (double free; although nothing obvious stands out). Running valgrind hasn't really helped a lot. Is this a known boost issue in 1.39.0?
Could you provide the exact error message, including any backtraces? If you get a similar error under valgrind, also provide complete error message from it.
I am using non-multithreaded versions of the boost libs: program-options, regex, iostreams, python, filesystem, system, date_time, unit_test_framework, and multithreaded version only for boost lib: thread.
This is non-starter. You should use MT versions of everything. Please make sure you link to MT versions of *every* boost library, and that every source file in your project is compiled with the -pthread option. Only then see if the issue reproduces. - Volodya
participants (2)
-
Sunil Thomas
-
Vladimir Prus