Subject: Re: [Boost-bugs] [Boost C++ Libraries] #12554: boost/core/typeinfo.hpp creates unwanted strings in release binary
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2016-11-01 07:31:39
#12554: boost/core/typeinfo.hpp creates unwanted strings in release binary
------------------------------------+---------------------
Reporter: Lev Sch <Zorechfan@â¦> | Owner: pdimov
Type: Bugs | Status: new
Milestone: To Be Determined | Component: core
Version: Boost 1.62.0 | Severity: Problem
Resolution: | Keywords:
------------------------------------+---------------------
Comment (by Lev Sch <Zorechfan@â¦>):
Summary:
1. my code must not put code strings into an executable
2. third party code must not put my code strings into an executable
3. third party code can put third party code strings into an executable,
but it is not desired
I'm developing under Android also. Every string is doubled (x86 and Arm
platforms).
Currently, after patch was applied from Description, following strings are
put into executable also (Android x86):
{{{
boost::filesystem::canonical
boost::filesystem::copy
boost::filesystem::copy_directory
boost::filesystem::copy_file
boost::filesystem::create_directories
boost::filesystem::create_directory
boost::filesystem::create_directory_symlink
boost::filesystem::create_hard_link
boost::filesystem::create_symlink
boost::filesystem::current_path
boost::filesystem::equivalent
boost::filesystem::file_size
boost::filesystem::hard_link_count
boost::filesystem::is_empty
boost::filesystem::last_write_time
boost::filesystem::permissions
boost::filesystem::read_symlink
boost::filesystem::relative
boost::filesystem::remove
boost::filesystem::remove_all
boost::filesystem::rename
boost::filesystem::resize_file
boost::filesystem::space
boost::filesystem::status
boost::filesystem::temp_directory_path
boost::filesystem::weakly_canonical
boost::filesystem::directory_iterator::construct
boost::filesystem::directory_iterator::operator++
boost::condition_variable::wait failed in pthread_cond_wait
boost unique_lock has no mutex
boost unique_lock doesn't own the mutex
boost unique_lock owns already the mutex
boost: mutex lock failed in pthread_mutex_lock
boost::condition_variable::do_wait_until failed in
pthread_cond_timedwait
boost::exception_ptr
boost::exception_detail::get_static_exception_object() [Exception =
boost::exception_detail::bad_alloc_]
C:\lib\boost_1_62_0\boost/exception/detail/exception_ptr.hpp
boost::exception_ptr
boost::exception_detail::get_static_exception_object() [Exception =
boost::exception_detail::bad_exception_]
boost:: mutex constructor failed in pthread_mutex_init
boost::condition_variable::condition_variable() constructor failed in
pthread_mutex_init
boost::condition_variable::condition_variable() constructor failed in
detail::monotonic_pthread_cond_init
static const char
*boost::detail::ctti<boost::algorithm::detail::token_finderF<boost::algorithm::detail::is_any_ofF<char>
> >::n() [T =
boost::algorithm::detail::token_finderF<boost::algorithm::detail::is_any_ofF<char>
>]
call to empty boost::function
bad lexical cast: source type value could not be interpreted as target
N5boost18thread_interruptedE
N5boost9exceptionE
N5boost16exception_detail10clone_baseE
N5boost16exception_detail10clone_implINS0_10bad_alloc_EEE
N5boost16exception_detail10bad_alloc_E
N5boost16exception_detail10clone_implINS0_14bad_exception_EEE
N5boost16exception_detail14bad_exception_E
}}}
Following compiler flags were used:
{{{
"-DANDROID",
"-DANDROID_NDK",
"-DBOOST_NO_TYPEID",
"-DBOOST_FILESYSTEM_NO_DEPRECATED",
"-DLOKI_OBJECT_LEVEL_THREADING",
"-DBOOST_ENABLE_ASSERT_DEBUG_HANDLER",
"-DBOOST_EXECUTION_CONTEXT=1",
"-fPIC",
"-fvisibility=hidden",
"-fvisibility-inlines-hidden",
"-ffunction-sections",
"-fdata-sections",
"-fno-rtti",
"-g",
"-Os",
"-DNDEBUG",
"-U_DEBUG",
}}}
-- Ticket URL: <https://svn.boost.org/trac/boost/ticket/12554#comment:9> Boost C++ Libraries <http://www.boost.org/> Boost provides free peer-reviewed portable C++ source libraries.
This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:20 UTC