You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the dmrpp_module/testsuite/bes.conf.in file both the runtime loadable modules
libdmrpp_module.so
libbuilddmrpp_module.so
are loaded into besstandalone from the bes.conf file in the modules/dmrpp_module /testsuite directory. This causes ODR violations to be detected by ASAN. The first error encountered is the redefinition of http/HttpError.cc
The obvious fix here is to simply eliminate the use of libbuilddmrpp_module.so from the bes.conf.in because it's not used in these tests. I removed it and ASAN was happy and all the tests behaved as expected.
But it is an outstanding question as to why this ODR violation happened given that we load lots of modules. Is this something we need to address in how we structure our build/deployment?
Inquiring minds want to know.
The text was updated successfully, but these errors were encountered:
In the
dmrpp_module/testsuite/bes.conf.in
file both the runtime loadable moduleslibdmrpp_module.so
libbuilddmrpp_module.so
are loaded into
besstandalone
from thebes.conf
file in themodules/dmrpp_module /testsuite
directory. This causes ODR violations to be detected by ASAN. The first error encountered is the redefinition ofhttp/HttpError.cc
The obvious fix here is to simply eliminate the use of
libbuilddmrpp_module.so
from thebes.conf.in
because it's not used in these tests. I removed it and ASAN was happy and all the tests behaved as expected.But it is an outstanding question as to why this ODR violation happened given that we load lots of modules. Is this something we need to address in how we structure our build/deployment?
Inquiring minds want to know.
The text was updated successfully, but these errors were encountered: