- Boost-users - lists.preview.boost.org

[asio]Why std::ofstream AND boost::asio::async_read() fails?
by Yasuhiko Yoshimura (informax.co.jp) 21 Sep '10

21 Sep '10

Hi All, I'm not able to see why downloading is sometimes fails in asio asyncread(). And I appriciate any suggestion. When 'comment===>> //' and 'insert ===>>' lines are valid, download file size is sometimes short than the original size from internet server(with big files). But if I put 'comment===>> //' back to no comment and remove 'insert ===>>' lines, the downloading result is perfect. class ftp_client_dtp { ... void start() { work_resolver_.reset(new boost::asio::ip::tcp::resolver(work_io_service_)); work_socket_.reset(new boost::asio::ip::tcp::socket(work_io_service_)); work_.reset(new boost::asio::io_service::work(work_io_service_)); work_thread_.reset(new boost::thread( boost::bind(&boost::asio::io_service::run, &work_io_service_))); ... comment===>> // std::string spath = scurrentpath_ + "\\" + sfilename_; comment===>> // f.open(spath.c_str(), std::ios::binary | std::ios_base::out); ... } ... void handle_read_content(const boost::system::error_code& err) { if (!err) { insert ===>> std::string spath = scurrentpath_ + "\\" + sfilename_; insert ===>> f.open(spath.c_str(), std::ios::binary | std::ios_base::out | std::ios_base::app); if (response_.size() > 0) { f << &response_; } insert ===>> f.close(); // Continue reading remaining data until EOF. boost::asio::async_read(*work_socket_, response_, boost::asio::transfer_at_least(1), boost::bind(&ftp_client_dtp::handle_read_content, shared_from_this(), boost::asio::placeholders::error)); } else if (err == boost::asio::error::eof) { // eof std::cout << err; insert ===>> std::string spath = scurrentpath_ + "\\" + sfilename_; insert ===>> f.open(spath.c_str(), std::ios::binary | std::ios_base::out | std::ios_base::app); if (response_.size() > 0) { f << &response_; } insert ===>> f.close(); do_close(); } else { std::cout << err; do_close(); } } void do_close() { comment===>> // f.close(); ... } std::ofstream f; std::string sip_, sport_, scurrentpath_, sfilename_; ... boost::asio::streambuf response_; ... };

1 0

[Serialization] Problem serializing directly and through base pointer in the same program.
by Travis Abbott 21 Sep '10

21 Sep '10

Hi, I am using Boost.Serialization to serialize classes through a shared_ptr to an abstract base class. Sometimes, I also serialize these classes directly. This was working for me in version 1.40, but not versions 1.41 or 1.44. If I serialize only shared_ptr<BaseClass> instances, everything is fine. If I link in code that serializes the derived class directly, even if that code is never called, serialization of shared_ptr<BaseClass> instances throws an exception ("unregistered class"). A few notes about what I am doing: I am calling BOOST_CLASS_EXPORT in the implementation file for each serializable class. I am using a template function for serialization that accepts any serializable type, creates a new text_oarchiver on the stack, and returns a string. This is called from many places in my application with many different types of things (making it hard to have a central place to put all the BOOST_CLASS_EXPORTs). I am having this problem on RHEL5 with gcc 4.1.2 WITHOUT optimization turned on. It works as expected with -O1 or higher. On WinXP with Visual Studio 2005, it fails in both release and debug mode. The problem also seems to depend on the order that the object files get written into the executable. If I include the file that is calling BOOST_CLASS_EXPORT first, things work as expected, but fail otherwise. (e.g., g++ obj.cpp main.cpp ... works, g++ main.cpp obj.cpp ... fails). Here are 3 source files, obj.h, obj.cpp, main.cpp that demonstrate this problem. The line in main: fromString(toString(obj), obj2); causes the code just before it (using shared_ptr) to fail. If anyone can let me know if I am misusing the library somehow, or if there is a cleaner way to accomplish what I am trying to do, I would be very appreciative. Thanks, Travis Abbott --------------------------8< obj.h 8< -------------------------- #pragma once #include <boost/serialization/void_cast.hpp> #include <string> class Base { public: virtual ~Base() {} virtual std::string name() const = 0; }; class Obj : public Base { public: std::string name() const { return "Obj"; } template<typename Arch> void serialize(Arch& arch, const unsigned version) { boost::serialization::void_cast_register<Obj, Base>( static_cast<Obj*>(NULL), static_cast<Base*>(NULL)); arch & data; } int data; }; --------------------------8< obj.cpp 8< -------------------------- #include "obj.h" #include <boost/archive/text_oarchive.hpp> #include <boost/archive/text_iarchive.hpp> #include <boost/serialization/export.hpp> BOOST_CLASS_EXPORT(Obj) --------------------------8< main.cpp 8< -------------------------- #include "obj.h" #include <boost/serialization/shared_ptr.hpp> #include <boost/archive/text_iarchive.hpp> #include <boost/archive/text_oarchive.hpp> #include <boost/shared_ptr.hpp> #include <iostream> #include <sstream> #include <stdexcept> #include <string> using boost::shared_ptr; using namespace std; template<typename T> string toString(const T& obj) { ostringstream ss; boost::archive::text_oarchive arch(ss); arch << obj; return ss.str(); } template<typename T> void fromString(const string& s, T& obj) { istringstream ss(s); boost::archive::text_iarchive arch(ss); arch >> obj; } int main() { try { shared_ptr<Base> pobj(new Obj), pobj2; fromString(toString(pobj), pobj2); cout << pobj2->name() << endl; // Compiling this causes runtime failure in code above. Obj obj, obj2; fromString(toString(obj), obj2); cout << obj2.name() << endl; } catch (const exception& e) { cerr << "Error: " << e.what() << endl; } return 0; }

2 2

boost serialisation 1.44 /linux /gcc 4.2.1 boost serialisation 1.44 /linux /gcc 4.2.1 boost serialisation 1.44 /linux /gcc 4.2.1 boost serialisation 1.44 /linux /gcc 4.2.1 boost serialisation 1.44 /linux /gcc 4.2.1 Re:boost serialisatio
by Avi Bahra 21 Sep '10

21 Sep '10

> Having problems with boost 1.44 and serialisation on Linux, gcc 4.2.1 > I am migrating from boost 1.43 to boost 1.44 > and get compiler errors of the form: > > In file included from ACore/src/TimeSeries.hpp:13, > from ACore/test/TestTimeSeries.cpp:16: > /var/tmp/ma0/boost/boost_1_44_0/boost/date_time/posix_time/time_serialize.hpp: > In function ?void boost::serialization::save(Archive&, const > boost::posix_time::time_duration&, unsigned int)?: > /var/tmp/ma0/boost/boost_1_44_0/boost/date_time/posix_time/time_serialize.hpp:42: > error: there are no arguments to ?make_nvp? that depend on a template > parameter, so a declaration of ?make_nvp? must be available > > This is surprising as boost 1.44 release notes makes no mention of any > changes to boost serialisation ? > > Can anyone help ? > Bryce Lelbach wrote: >>Looks like a problem with date_time, not serialization. I know 1.44 builds on >>GNU/Linux GCC 4.2.1 for me. >> >>Can you make sure you have a file at >>/var/tmp/ma0/boost/boost_1_44_0/boost/serialization/nvp.hpp? If you do have it, >>could you show us? I just downloaded boost 1.44 today: The file: /var/tmp/ma0/boost/boost_1_44_0/boost/serialization/nvp.hpp exist. This is what I have: //=============================================================== #ifndef BOOST_SERIALIZATION_NVP_HPP #define BOOST_SERIALIZATION_NVP_HPP // MS compatible compilers support #pragma once #if defined(_MSC_VER) && (_MSC_VER >= 1020) # pragma once #endif /////////1/////////2/////////3/////////4/////////5/////////6/////////7/////////8 // nvp.hpp: interface for serialization system. // (C) Copyright 2002 Robert Ramey - http://www.rrsd.com . // Use, modification and distribution is subject to the Boost Software // License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at // http://www.boost.org/LICENSE_1_0.txt) // See http://www.boost.org for updates, documentation, and revision history. #include <utility> #include <boost/config.hpp> #include <boost/detail/workaround.hpp> // supress noise #if BOOST_WORKAROUND(BOOST_MSVC, <= 1200) # pragma warning (disable : 4786) // too long name, harmless warning #endif #include <boost/mpl/integral_c.hpp> #include <boost/mpl/integral_c_tag.hpp> #include <boost/serialization/level.hpp> #include <boost/serialization/tracking.hpp> #include <boost/serialization/split_member.hpp> #include <boost/serialization/base_object.hpp> #include <boost/serialization/traits.hpp> #include <boost/serialization/wrapper.hpp> namespace boost { namespace serialization { template<class T> struct nvp : public std::pair<const char *, T *>, public wrapper_traits<const nvp<T> > { explicit nvp(const char * name_, T & t) : // note: redundant cast works around borland issue // note: added _ to suppress useless gcc warning std::pair<const char *, T *>(name_, (T*)(& t)) {} nvp(const nvp & rhs) : // note: redundant cast works around borland issue std::pair<const char *, T *>(rhs.first, (T*)rhs.second) {} const char * name() const { return this->first; } T & value() const { return *(this->second); } const T & const_value() const { return *(this->second); } // True64 compiler complains with a warning about the use of // the name "Archive" hiding some higher level usage. I'm sure this // is an error but I want to accomodated as it generates a long warning // listing and might be related to a lot of test failures. // default treatment for name-value pairs. The name is // just discarded and only the value is serialized. template<class Archivex> void save( Archivex & ar, const unsigned int /* file_version */ ) const { // CodeWarrior 8.x can't seem to resolve the << op for a rhs of "const T *" ar.operator<<(const_value()); } template<class Archivex> void load( Archivex & ar, const unsigned int /* file_version */ ){ // CodeWarrior 8.x can't seem to resolve the >> op for a rhs of "const T *" ar.operator>>(value()); } BOOST_SERIALIZATION_SPLIT_MEMBER() }; template<class T> inline #ifndef BOOST_NO_FUNCTION_TEMPLATE_ORDERING const #endif nvp<T> make_nvp(const char * name, T & t){ return nvp<T>(name, t); } // to maintain efficiency and portability, we want to assign // specific serialization traits to all instances of this wrappers. // we can't strait forward method below as it depends upon // Partial Template Specialization and doing so would mean that wrappers // wouldn't be treated the same on different platforms. This would // break archive portability. Leave this here as reminder not to use it !!! #if 0 // #ifndef BOOST_NO_TEMPLATE_PARTIAL_SPECIALIZATION template <class T> struct implementation_level<nvp<T> > { typedef mpl::integral_c_tag tag; typedef mpl::int_<object_serializable> type; BOOST_STATIC_CONSTANT(int, value = implementation_level::type::value); }; // nvp objects are generally created on the stack and are never tracked template<class T> struct tracking_level<nvp<T> > { typedef mpl::integral_c_tag tag; typedef mpl::int_<track_never> type; BOOST_STATIC_CONSTANT(int, value = tracking_level::type::value); }; #endif } // seralization } // boost #include <boost/preprocessor/stringize.hpp> #define BOOST_SERIALIZATION_NVP(name) \ boost::serialization::make_nvp(BOOST_PP_STRINGIZE(name), name) /**/ #define BOOST_SERIALIZATION_BASE_OBJECT_NVP(name) \ boost::serialization::make_nvp( \ BOOST_PP_STRINGIZE(name), \ boost::serialization::base_object<name >(*this) \ ) /**/ #endif // BOOST_SERIALIZATION_NVP_HPP // ======================================== Best regards, Ta, Avi

2 1

Using boost::interprocess shared memory for both 32-bit and 64-bit processes
by Jonathon 21 Sep '10

21 Sep '10

Hello, I would like to read/write from/to boost::interprocess shared memory segments from a 32-bit process and a 64-bit process on the same machine. Is this possible? I've attempted to do this, but I seem to be experiencing some compatibility issues. Note that I am reading/writing boost::inteprocess containers to shared memory. For example, in my 32-bit process, I'll add some data to a boost::interprocess::vector and when I read this data from my 64-bit process, it returns garbage. Are there compiler options I can set to make things compatible? If it is not possible to do this, what are some possible solutions for this? Thanks, J

3 2

[multi_array] why this does not compile? allocator?
by Suresh Kumar 20 Sep '10

20 Sep '10

Could you kindly tell me why the following code does not compile? I guess it is an allocator issue, but how do I go further? #include <boost/multi_array.hpp> #include <iostream> using namespace std; int main () { class test{ int x; int y; }; typedef boost::multi_array<test, 3> array_type; typedef array_type::index index; array_type A(boost::extents[3][4][2]); array_type::extent_gen extents; return 0; } compile errors: multiArray.cpp:11: error: template argument for ‘template<class _Alloc> class std::allocator’ uses local type ‘main()::test’ multiArray.cpp:11: error: trying to instantiate ‘template<class _Alloc> class std::allocator’ multiArray.cpp:11: error: template argument 3 is invalid multiArray.cpp:11: error: invalid type in declaration before ‘;’ token multiArray.cpp:12: error: expected initializer before ‘index’ multiArray.cpp:13: error: cannot convert ‘boost::detail::multi_array::extent_gen<3ul>’ to ‘array_type’ in initialization multiArray.cpp:14: error: expected initializer before ‘extents’ -- R Suresh Kumar, http://www.ee.ucr.edu/~sramachandranna Sarve bhavantu sukinaha (May everyone be happy) Sarve santu niramiyaha (May everyone be without affliction) Sarve bhadrani pashyantu (May everyone see only goodness) Ma kashchit dukha bhak bhavet (Let none be the victim of suffering)

2 1

[Fusion] fusion::for_each with stateful functors
by Paul Graphov 20 Sep '10

20 Sep '10

Hello Boost Users, More than three years ago this question arose in this list: http://lists.boost.org/boost-users/2007/03/26338.php And as I understand it was concluded that overload for non-const references should be added. But now there are only const references to functor available. Was it forgotten or there are some reasons not to have such overload? What is the best way to solve the problem? Mutable members or some proxies look quirky. Thanks!

3 3

Re: [Boost-users] [SmartPtr] Memory Leak Perhaps
by Benjamin Sobotta 20 Sep '10

20 Sep '10

On Monday 20 September 2010 02:44:12 pm you wrote: > Dear Benjamin, > > > shared_ptr to this are dangerous. As soon as you do that > > twice you already have a problem. > > Oh, that's interesting. Could you please explain why? Well because you can only erase 'this' once. When you have two _independent_ smart pointers, both will attempt to delete the object they're pointing to. > > > If you want to create shared_ptrs to this, use > > shared_from_this. > > > > http://www.boost.org/doc/libs/1_44_0/libs/smart_ptr/enable_shared_from_th > >is.html > > Thank you for the reference. At the very bottom of the documentation, I see > "There must exist at least one shared_ptr instance p that owns t" (in the > requirements of template<class T> shared_ptr<T const> > enable_shared_from_this<T>::shared_from_this() const). So, does the > following code not meet this requirement? > > class Y: public T, public boost::enable_shared_from_this<Y> > { > public: > > boost::shared_ptr<Y> f() const > { > return shared_from_this(); > } > }; > > const T* tp = new Y;//where Y also derives from T > boost::shared_ptr<T> q = tp->f(); Yes, as far as I know this won't work. But why would you want that? boost::shared_ptr<T> q = boost::make_shared<Y>(); is the safe way to do it. No explicit 'new', no explicit 'delete', no problems. Call your insert_me_into routine through the shared_ptr. Then, inside insert_me_into, after you're done with your computations, use shared_from_this to get a shared_ptr to stick into the container. > TIA, > --Hossein HTH, Benjamin

1 0

[SmartPtr] Memory Leak Perhaps
by Hossein Haeri 20 Sep '10

20 Sep '10

Dear all, (Sorry for cross-posting.) I have a container which stores boost::shared_ptr's. The container has a strange behaviour upon insertion of a SPECIFIC pointer into it. The insertion itself happens with no problem and I can successfully do all my desired operations. Yet, I receive the following strange Win32 exceptions when I'm done and my program is ending (i.e., after the last instruction in my main function): 1) When I run the program from the CodeBlocks IDE (GCC 4.5.1, MinGW, WinXP-SP3), a message box from the JIT debugger pops up which says: "An unhandled Win32 exception occurred in ... [29436]". 2) When I run the same program from MSCV2008, an MSVC++ Debug Library message box pops up which says: "Program ... File f:\dd\... Line 52 Exception _BLOCK_TYPE_IS_VALID(pHead->nBlockUse)...". I call the above error messages strange because of the observations below: 1) The error reported by MSVC2008 refers to a file on my drive F: whereas, basically, I don't have such a drive on my system! 2) The CodeBlocks debugger (a GUI wrapped around GDB) runs the program with no problems over the debug sessions. Despite that, there are several "Program received signal SIGTRAP, Trace/breakpoint trap." messages in the GDB debug log. Unfortunately, I don't know how to locate the place where these are related to. 3) MSVC2008 has the same behaviour over the debug session. The output of debug session ends with "The program '[29312] EE1Debugger.exe: Native' has exited with code 3 (0x3)." (Please find a copy of the debug log at the P.S. if you're interested.) My first guess was a memory leak but I didn't spot anything which smells like that over numerous debug sessions. I'm generally dubious about that because I'm using shared_ptr's. Shallow copy can't be the problem either again 'cause I only insert shared_ptr's (from just-allocated dynamic memory) into my container. On the other hand, the problem only occurs upon insertion of a SPECIFIC entry into my container. Strangely enough, if I delete that specific entry manually before the end of my program, everything goes fine! I even checked the count of that specific shared_ptr and it was 1, i.e., I'm not deleting anybody else's memory. I am really confused and left with no clue... Any suggestions? P.S. 'EE1Debugger.exe': Loaded 'D:\...\EE1Debugger.exe', Symbols loaded. 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\ntdll.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\kernel32.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\WinSxS\x86_Microsoft.VC90.DebugCRT_1fc8b3b9a1e18e3b_9.0.21022.8_x-ww_597c3456\msvcr90d.dll', Symbols loaded. 'EE1Debugger.exe': Loaded 'C:\WINDOWS\WinSxS\x86_Microsoft.VC90.DebugCRT_1fc8b3b9a1e18e3b_9.0.21022.8_x-ww_597c3456\msvcp90d.dll', Symbols loaded. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f550.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\user32.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\gdi32.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\imm32.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\advapi32.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\rpcrt4.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\secur32.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\lpk.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\usp10.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\msvcrt.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\GDX32.dll', Binary was not built with debug information. 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\acaptuser32.dll', Binary was not built with debug information. 'EE1Debugger.exe': Unloaded 'C:\WINDOWS\system32\acaptuser32.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\uxtheme.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\MSCTF.dll' 'EE1Debugger.exe': Loaded 'C:\Program Files\Trusteer\Rapport\bin\rooksbas.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\version.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\shlwapi.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\psapi.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\shell32.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\ole32.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.5512_x-ww_35d4ce83\comctl32.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\comctl32.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\MSCTFIME.IME' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\PickWord.dll', Binary was not built with debug information. 'EE1Debugger.exe': Loaded 'C:\Program Files\Dell\QuickSet\dadkeyb.dll', Binary was not built with debug information. 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\hccutils.dll', Binary was not built with debug information. 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\oleaut32.dll' The program '[29312] EE1Debugger.exe: Native' has exited with code 3 (0x3).

4 5

boost serialisation 1.44 /linux /gcc 4.2.1 compilation problems
by avibahra 20 Sep '10

20 Sep '10

Having problems with boost 1.44 and serialisation on Linux, gcc 4.2.1 I am migrating from boost 1.43 to boost 1.44 and get compiler errors of the form: In file included from ACore/src/TimeSeries.hpp:13, from ACore/test/TestTimeSeries.cpp:16: /var/tmp/ma0/boost/boost_1_44_0/boost/date_time/posix_time/time_serialize.hpp: In function ‘void boost::serialization::save(Archive&, const boost::posix_time::time_duration&, unsigned int)’: /var/tmp/ma0/boost/boost_1_44_0/boost/date_time/posix_time/time_serialize.hpp:42: error: there are no arguments to ‘make_nvp’ that depend on a template parameter, so a declaration of ‘make_nvp’ must be available This is surprising as boost 1.44 release notes makes no mention of any changes to boost serialisation ? Can anyone help ? Best regards, Ta, Avi

2 1

Re: [Boost-users] boost::bond and assignment
by przemyslaw.sliwa＠uk.bnpparibas.com 20 Sep '10

20 Sep '10

Thank, This is true if you have a boost::shared_ptr<int> but in my case I have a class not an int and I want to assign a value of one of its members called mem, for(vector<clss>::iterator pos=tmp.begin(); pos!=tmp.end(); ++tmp) { clss& item = (*pos); item.mem = 1.0; } how this can be translated into the boost lambda or bind? Cheers ___________________________________________________________ This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is prohibited. Please refer to http://www.bnpparibas.co.uk/en/information/legal_information.asp?Code=ECAS-… for additional disclosures.

2 1