State:Closed|icon_bug|icon_katana|database:public|Resolution:Fixed|TargetRelease:3.2v2|BugID:406453|
Problem summary:
Unfortunately it appears there are slight differences between the Boost 1.61 binaries we have and the ones shipped with Katana, which turns out to be problematic at run-time, making Katana 3.2v1 unstable.
Here is an example (on closing Katana):
*** Error in `/rel/third_party/katana/3.2v1/bin/python/Main/Main.pyc': double free or corruption (!prev): 0x0000000007a60740 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x81609)[0x7f6489d74609]
/lib64/libstdc++.so.6(_ZNSsD1Ev+0x43)[0x7f648a393b63]
/lib64/libc.so.6(__cxa_finalize+0x9a)[0x7f6489d2cf9a]
/rel/third_party/katana/3.2v1/bin/libboost_program_options.so.1.61.0(+0x29193)[0x7f648ded5193]
I can confirm there are slight differences between our libboost_program_options.so.1.61.0 and the one shipped with Katana, which may be caused by using different build-time boost-specific macros to customize the build (for instance our binary contains symbols with r-value references, but there are no r-value references in the Boost.Program_options binary shipped with Katana).
Unfortunately it appears adopting Katana 3.2v1 in its current form is not possible for us.
Steps to reproduce:
Close Katana
Expected behaviour:
No error message appears
Actual behaviour:
Error message appears
*** Error in `/rel/third_party/katana/3.2v1/bin/python/Main/Main.pyc': double free or corruption (!prev): 0x0000000007a60740 *** ======= Backtrace: ========= /lib64/libc.so.6(+0x81609)[0x7f6489d74609] /lib64/libstdc++.so.6(_ZNSsD1Ev+0x43)[0x7f648a393b63] /lib64/libc.so.6(__cxa_finalize+0x9a)[0x7f6489d2cf9a] /rel/third_party/katana/3.2v1/bin/libboost_program_options.so.1.61.0(+0x29193)[0x7f648ded5193]
Workaround:
No known workaround.
Tested versions/platforms:
Customer version/platform:
Not supplied
We're sorry to hear that
Please tell us why