- Boost-users - lists.boost.org

"invalid signature" in boost::archive::binary_iarchive
by Ibrahim Beicker 28 May '12

28 May '12

I had to port a multi-process application to 64 bits and I rely on boost serialization to send messages, that are maps of key-values, into Microsoft queues to the other modules. It works just fine into 32 bits but when I run it in 64 the constructor throws an "invalid signature" exception void Message::fromBinary( const std::string& data ) { std::stringstream ss; ss << data; boost::archive::binary_iarchive ia(ss); //exception here ia >> *this; } I managed to debug into basic_binary_iarchive.ipp and this 'if' @ line 72 fails if(file_signature != BOOST_ARCHIVE_SIGNATURE()) boost::serialization::throw_exception(archive_exception(archive_exception::invalid_signature)); inside this file I have no debug symbols so I don't know the values of 'file_signature' and 'BOOST_ARCHIVE_SIGNATURE' or where BOOST_ARCHIVE_SIGNATURE is defined. Some additional information: the modules are all running on the same machine, on windows 7 64-bits, and compiled by visual studio 2010 x64 including static boost libraries 1.45. What causes this and how can I fix it?

3 4

[asio] Using asio for asynchronous event processing
by Edward Diener 28 May '12

28 May '12

I do not understand the documentation for asio, or even if it pertains to the programming problem I am trying to solve. The doc, for whatever reason, is poor regarding practical use. But rather than complain about the doc I will ask a specific problem related to what I am trying to do and hopefully someone can help me or point me to something in the doc by which I can understand how to use asio for my problem. I need to design generalized asynchronous events triggered by an event source and handled by an event handler. The event source would trigger an event declared as a callable object, as in boost::function, and an event handler would eventually handle the event asynchronously. The event source and the event handler would be in different threads of an application but not in different applications. The event source triggers the event but does not block in any way waiting for the event to be processed. The event source may subsequently trigger other asynchronous events to be eventually handled in the same way without blocking. The event handler is able to check for events periodically from within its own thread. Each event itself could be a totally different callable object, but the event source and the event handler both know the callable prototype for any given event. The event source and the event handler are completely disconnected in that neither knows about the other. For any given asynchronous event there may be any number of event handlers when an event is triggered. Can I use asio to implement such a solution ? The doc suggests that asio does not only deal in i/o events, such as networking and sockets, but I could not understand whether it deals in generalized asynchronous operations or not. The proactor pattern is understandable but there appears to be nothing in the doc which connects the elements of the proactor pattern to classes in asio. The basic tutorial as well as the sockets tutorial does not enlighten me at all. Hopefully someone here can help.

2 2

Asynchronous signals library
by Edward Diener 28 May '12

28 May '12

The signals and signals2 library work with signals ( events ) which are handled synchronously. Is there any Boost library, based on the function prototyping methods of signals(2), in which the signals are handled asynchronously ?

3 4

BOOST_ALL_NO_LIB / BOOST_THREAD_NO_LIB / BOOST_THREAD_DYN_LINK etc etc etc
by Josh Quigley 28 May '12

28 May '12

Hi, I'm trying to link to Boost.Thread DLL's. If I define BOOST_ALL_NO_LIB everything works fine - but it wants to link all packages as DLL, instead of just Boost.Thread. None of the following cause dynamic linking - that is I get a linker error saying the static *.lib could not be found. (defined on the command line, Visual Studio 2010) BOOST_THREAD_NO_LIB BOOST_THREAD_DYN_LINK BOOST_THREAD_ALL_DYN_LINK BOOST_THREAD_BUILD_DLL BOOST_THREAD_USE_DLL Is there a problem with - what I'm doing; - Visual Studio 2010; or - boost.thread? Cheers, Josh.

2 1

arm-elf-gcc 4.0.1 class alignment
by Pierre-Andre van Leeuwen 28 May '12

28 May '12

Hi Not sure if this belongs on this list or the Boost.Build list, but the problem exists when using Boost as well as building it. I'm using Boost with the ARM-ELF-GCC toolchain with gcc version 4.0.1. When building the Boost serialization library, I get the following error: ./boost/archive/basic_binary_oarchive.hpp:80: error: invalid application of 'sizeof' to incomplete type 'boost::STATIC_ASSERTION_FAILURE<false>' It turns out that sizeof(class_id_type ) == 4 in stead of 2, where class_id_type is defined as follows: class class_id_type { private: typedef int_least16_t base_type; base_type t; ... }; Using a toolchain with a more recent gcc version (arm-none-eabi-gcc 4.4.1) works correctly, but unfortunately I need to get Boost working with the old toolchain as well. I have tried to add __attribute__ ((packed)) to the class declaration, but that breaks as well (cannot bind packed field in operator int_least16_t). Is there anything I can do to rectify the situation? My user-config.jam contains the following: using gcc : armelf : "arm-elf-gcc.exe" : <cflags>-nostdlib <cxxflags>-DBOOST_NO_INTRINSIC_WCHAR_T <cxxflags>-D__OAT_API_VERSION__=637 <cxxflags>-D__WIP_PLUGIN_VERSION__=543 <cxxflags>-D__arm <cxxflags>-D_LITTLE_ENDIAN <cxxflags>-IC:\Program Files (x86)\Sierra Wireless\Embedded Software\com.wavecom.openat.ide.spm.lib.os.model.6.37.0.201202060950_6.37.0.201202060950\resources/ADL/itf <cxxflags>-IC:\Program Files (x86)\Sierra Wireless\Embedded Software\com.wavecom.openat.ide.spm.lib.os.model.6.37.0.201202060950_6.37.0.201202060950\resources/ADL/basic <cxxflags>-IC:\Program Files (x86)\Sierra Wireless\Embedded Software\com.wavecom.openat.ide.spm.lib.plugin.model.WIP.5.43.0.201202100610_5.43.0.201202100610\resources/WIP/itf <cxxflags>-fshort-enums <cxxflags>-fdollars-in-identifiers <cxxflags>-nostartfiles <cxxflags>-fno-strict-aliasing <cxxflags>-fno-common <cxxflags>-fomit-frame-pointer <cxxflags>-mthumb-interwork <cxxflags>-mthumb <cxxflags>-march=armv5te <cxxflags>-msoft-float <cxxflags>-mfpu=fpa <cxxflags>-mapcs <cxxflags>-mno-apcs-stack-check <cxxflags>-mlittle-endian <architecture>arm <address-model>32 ; I'm building boost with the following command .\b2 variant=debug,release link=static threading=single toolset=gcc-armelf --debug-configuration --debug-building --with-serialization stage Any help will be appreciated. Pierre-Andre van Leeuwen Director | Gendac (Pty) Ltd<http://www.gendac.com/>

1 0

mpl and fusion containers: numbered vs variadic
by MM 27 May '12

27 May '12

Hello, Is it true that as a general rule, using the numbered version instead of the variadic version yields faster compile times? Or is it just about compilers supporting variadic templates? MM

3 3

BOOST_RESULT_OF_USE_DECLTYPE and Boost.Optional ?
by John M. Dlugosz 27 May '12

27 May '12

I turned on BOOST_RESULT_OF_USE_DECLTYPE and used boost::result_of because the std::tr1::result_of that comes with VS10 doesn't use declspec at all and thus doesn't work right with lambda functions. This passes my unit tests, but fails on a piece of code that has a function returning an instantiation of boost::optional. It seems confused as to whether the value held in the optional is as-specified or has a reference added to it. I wonder if this is a specific issue with optional that might be addressed/worked-around/patched, or perhaps there is a way to enable declspec-based testing just for the code that wanted it and not globally? —John

2 1

Why does the fusion::set repeated keys?
by niXman 27 May '12

27 May '12

Hi, In this simple code, I expect that the size of the fusion::set is equal to one, because keys are the same. Why the size is equal to two? #include <boost/fusion/container/set.hpp> #include <boost/fusion/include/set.hpp> #include <boost/fusion/container/set/set_fwd.hpp> #include <boost/fusion/include/set_fwd.hpp> #include <boost/fusion/sequence/intrinsic/size.hpp> #include <boost/fusion/include/size.hpp> #include <iostream> int main() { typedef boost::fusion::set<int, int> set1; set1 s1; std::cout << "size1 = " << boost::fusion::result_of::size<set1>::type::value << ", size2 = " << boost::fusion::size(s1) << std::endl; } http://liveworkspace.org/code/166b54cdd208f7b252bf1f38a1a6ec4b Thanks! -- Regards, niXman ___________________________________________________ Dual-target(i686/x86_64) MinGW compiler for i686/x86_64 hosts: http://sourceforge.net/projects/mingwbuilds/

2 1

[asio] Boost asio mailing list
by Edward Diener 27 May '12

27 May '12

How do I subscribe to the asio mailing list ?

2 1

BOOST_RESULT_OF_USE_DECLTYPE and Boost.Optional ?
by John M. Dlugosz 27 May '12

27 May '12

Hmm, the error isn't quite what I said: 1>V:\Trunk\stable\src\Include\Tools/async.h(268): error C2664: 'boost::unique_future<R>::unique_future(boost::unique_future<R> &)' : cannot convert parameter 1 from 'boost::unique_future<R>' to 'boost::unique_future<R> &' 1> with 1> [ 1> R=boost::optional<in_addr> & 1> ] 1> and 1> [ 1> R=boost::optional<in_addr> 1> ] 1> and 1> [ 1> R=boost::optional<in_addr> & 1> ] But my other test cases of using unique_future (with simple types) work OK. —John

1 0