- Boost-users - lists.boost.org

[Interprocess] Using shared Memory with different compilers (msvc, mingw)
by BaDBuTz 29 Oct '09

29 Oct '09

hi, My library uses boost::interprocess' Shared Memory and has to be delivered with msvc(7.1) and mingw compiled versions. Every instance of the that library opens a connection to the Shared Memory "sharedMemoryMapTest" and communicates via instances of the class "SyncObject". In my test program ProcessA opens the shared memory, instanciates a SynObject with the identifyer String "id1". ProcessB connects to the same SyncObject and synchronizes with ProcessA. If ProcessA and ProcessB are both compiled with the same compiler it works fine. If one process is compiled with mscv and the other is compiled with mingw it fails. (mscv = ProcessA, ProcessB = mingw -> I read my Windows environment variables instead of "id1") Did I make a mistake in my implementation, or is it simply not possible to access the same Shmem with different compiled versions? Thanks in advance Martin (compilable) code: #include <iostream> #include <boost/interprocess/managed_shared_memory.hpp> #include <boost/interprocess/allocators/allocator.hpp> #include <boost/interprocess/containers/string.hpp> #include <boost/interprocess/containers/list.hpp> typedef unsigned long U32; using namespace boost::interprocess; class SyncObject { public: SyncObject(std::string aId) : id(aId), locAddrSp0Range(0), locAddrSp0Remap(0), locAddrSp1Range(0), locAddrSp1Remap(0), usbInterfaceOwner(0), useCounter(0) {} ; ~SyncObject() { std::cout << "SyncObject Destructor\n" << std::flush; }; void print() { std::cout << " id = " << id << " locAddrSp0Range = " << locAddrSp0Range << " locAddrSp0Remap = " << locAddrSp0Remap << " locAddrSp1Range = " << locAddrSp1Range << " locAddrSp1Remap = " << locAddrSp1Remap << " usbInterfaceOwner = " << usbInterfaceOwner << " useCounter = " << useCounter << "\n" << std::flush; }; std::string id; interprocess_mutex mtxReadWrite; interprocess_mutex mtxFunction; U32 locAddrSp0Range; U32 locAddrSp0Remap; U32 locAddrSp1Range; U32 locAddrSp1Remap; U32 usbInterfaceOwner; U32 useCounter; }; const char* MANAGED_SHARED_MEMORY_NAME = "sharedMemoryMapTest58"; const char* SYNC_OBJ_LIST_NAME = "sharedMemorySyncList"; typedef offset_ptr<SyncObject> SyncObjOffsetPtr; typedef allocator<SyncObjOffsetPtr, managed_shared_memory::segment_manager> SyncObjOffsetPtrAllocator; typedef list<SyncObjOffsetPtr, SyncObjOffsetPtrAllocator> SyncObjectList; class SharedMemory { public: SharedMemory(); ~SharedMemory(); void printList(); SyncObject* getSyncObject(std::string id); void removeSyncObject(std::string id); private: managed_shared_memory segment; }; SharedMemory::SharedMemory() { segment = managed_shared_memory(open_or_create, MANAGED_SHARED_MEMORY_NAME, 65536); } SharedMemory::~SharedMemory() { std::cout << "SharedMemory Destuctor\n" << std::flush; SyncObjectList* pList = segment.find<SyncObjectList>(SYNC_OBJ_LIST_NAME).first; if (pList) { if (pList->size() < 1) { segment.destroy_ptr(pList); std::cout << "pList destroyed! \n" << std::flush; } } // unlink shared mem object // shared_memory_object::remove(MANAGED_SHARED_MEMORY_NAME); if( shared_memory_object::remove(MANAGED_SHARED_MEMORY_NAME)) std::cout << MANAGED_SHARED_MEMORY_NAME << " successfully removed from the system!\n" << std::flush; else std::cout << MANAGED_SHARED_MEMORY_NAME << " could not be removed from the system!\n" << std::flush; } void SharedMemory::printList() { SyncObjectList* pList = segment.find<SyncObjectList>(SYNC_OBJ_LIST_NAME).first; if (!pList) { std::cout << "List does not exist!\n" << std::flush; return; } std::cout << "list contains: "; for(SyncObjectList::iterator iter = pList->begin(); iter != pList->end(); ++iter ) { std::cout << iter->get()->id << "\t"; } std::cout << "\n" << std::flush; } SyncObject* SharedMemory::getSyncObject(std::string id) { //Initialize shared memory STL-compatible allocator const SyncObjOffsetPtrAllocator syncObjOffsetPtrAllocatorInst (segment.get_segment_manager()); SyncObjectList* pList = segment.find_or_construct<SyncObjectList>(SYNC_OBJ_LIST_NAME)(syncObjOffsetPtrAllocatorInst); printList(); for(SyncObjectList::iterator iter = pList->begin(); iter != pList->end(); ++iter ) { if (iter->get()->id == id) { std::cout << id << " already exists in SHMem! returning pointer\n"; iter->get()->useCounter++; return iter->get(); } } std::cout << id << " is not in the list and will be created in SHMem!\n"; SyncObject* ptr = segment.construct<SyncObject>(id.c_str())(id); ptr->useCounter++; pList->push_back(offset_ptr<SyncObject>(ptr)); return ptr; } void SharedMemory::removeSyncObject(std::string id) { //Initialize shared memory STL-compatible allocator const SyncObjOffsetPtrAllocator syncObjOffsetPtrAllocatorInst (segment.get_segment_manager()); SyncObjectList* pList = segment.find_or_construct<SyncObjectList>(SYNC_OBJ_LIST_NAME)(syncObjOffsetPtrAllocatorInst); printList(); for(SyncObjectList::iterator iter = pList->begin(); iter != pList->end(); ++iter ) { if (iter->get()->id == id) { if (iter->get()->useCounter < 2) { std::cout << "removing " << id << " from list \n" << std::flush; SyncObject *ptr = iter->get(); segment.destroy_ptr(ptr); pList->erase(iter); } else { std::cout << "decrementing userCounter of id " << id << "\n" << std::flush; iter->get()->useCounter--; } break; } } } int main() { try { SharedMemory shm; SyncObject *pSync = shm.getSyncObject("id1"); pSync->mtxFunction.lock(); pSync->print(); pSync->locAddrSp0Range++; pSync->print(); pSync->mtxFunction.unlock(); shm.removeSyncObject("id1"); pSync = shm.getSyncObject("id1"); pSync->mtxFunction.lock(); pSync->print(); pSync->locAddrSp0Range++; pSync->print(); pSync->mtxFunction.unlock(); shm.removeSyncObject("id1"); } catch(boost::interprocess::interprocess_exception &ex) { std::ostringstream sout; sout.str(""); sout << ex.what(); std::cout << sout.str() << std::flush; } return 0; } -- Neu: GMX DSL bis 50.000 kBit/s und 200,- Euro Startguthaben! http://portal.gmx.net/de/go/dsl02

3 3

[ptr_container] ptr_vector and ptr_circullar_buffer don't initialize PODs
by Roman Perepelitsa 29 Oct '09

29 Oct '09

ptr_vector<T>::resize creates new objects using 'new T' instead of 'new T()', which results in uninitialized objects if T is a POD. For consistency with STL containers (std::vector in particular) all PODs must be explicitly initialized. Test: #include <cassert> #include <boost/ptr_container/ptr_vector.hpp> int main() { boost::ptr_vector<int> v; v.resize(1); assert(v[0] == 0); // Might fail. } ptr_circullar_buffer has the same problem. I opened a trac ticket (https://svn.boost.org/trac/boost/ticket/3579) and attached a patch to it. Roman Perepelitsa.

1 0

[boost] Create Graph in Function
by James Thunes 29 Oct '09

29 Oct '09

Perhaps an easy answer, but I am working on adding a boost graph to an existing code. I would like to create the graph in a function (not main) and then read/modify it in a separate function. I am unsure as to what I need to pass between the functions to allow this to work. In other words, I am able to correctly create the graph in a function and modify as necessary. This function will be called many times as the code runs and it is inefficient to recreate the graph every time. I want to create the graph once when the code is run and pass the created graph to the function. Due to the structure of the code (mostly Fortran), I can not define the graph in the main function of the code. My graph is defined as: adjacency_list<vecS, vecS, bidirectionalS, no_property, EdgeProperty> Graph; Thank you for any help you can give, James

4 7

Multiple binds on a asio socket
by Lee MacDonald 29 Oct '09

29 Oct '09

Hi, Is it possible to have multiple binds on a single socket instance? Say I have two multicast addresses that share the same port and use the same nic. On linux I would bind like so: listenEndPoint1(multicastAddress1.to_v4(), port); socket_.bind(listenEndPoint1); socket_.set_option(asio::ip::multicast::join_group(multicastAddress1.to_ v4(), interfaceAddress.to_v4())); } Can I then perform a second bind and join for the other multicast address? listenEndPoint2(multicastAddress2.to_v4(), port); socket_.bind(listenEndPoint2); socket_.set_option(asio::ip::multicast::join_group(multicastAddress2.to_ v4(), interfaceAddress.to_v4())); } If this is not possible or good practice, what would be the alternative? Regards, Lee MacDonald Schneider Trading 4th Floor, 25 Copthall Avenue London EC2R 7BP ________________________________ Message from: lee.macdonald(a)schneidertrading.com Message to: asio-users(a)lists.sourceforge.net Attached files: 0 This e-mail and any files transmitted with it are confidential, may be legally privileged, and are for the sole use of the intended recipient. Copyright in this e-mail and any accompanying document created by us is owned by us. If you are not the intended recipient of this e-mail or any part of it please telephone our IT Department at the number shown above or by e-mail at info(a)schneidertrading.com. You should not use or disclose to any other person the contents of this e-mail or its attachments (if any), nor take copies. This e-mail is not a representation or warranty and is not intended nor should it be taken to create any legal relations, contractual or otherwise. Schneider Trading Associates Ltd (Registration No. 3692131) is incorporated in England and Wales and the registered office is at 25 Copthall Avenue, London EC2R 7BP. The company is authorised and regulated by the Financial Services Authority Schneider Trading 4th Floor, 25 Copthall Avenue London EC2R 7BP -------------------------------------------------------- Message from: lee.macdonald(a)schneidertrading.com Message to: boost-users(a)lists.boost.org Attached files: 0 This e-mail and any files transmitted with it are confidential, may be legally privileged, and are for the sole use of the intended recipient. Copyright in this e-mail and any accompanying document created by us is owned by us. If you are not the intended recipient of this e-mail or any part of it please telephone our IT Department at the number shown above or by e-mail at info(a)schneidertrading.com. You should not use or disclose to any other person the contents of this e-mail or its attachments (if any), nor take copies. This e-mail is not a representation or warranty and is not intended nor should it be taken to create any legal relations, contractual or otherwise. Schneider Trading Associates Ltd (Registration No. 3692131) is incorporated in England and Wales and the registered office is at 25 Copthall Avenue, London EC2R 7BP. The company is authorised and regulated by the Financial Services Authority

1 0

Re: [Boost-users] Signal handler for Unix platforms
by Boris Schaeling 29 Oct '09

29 Oct '09

On Wed, 28 Oct 2009 23:18:04 +0100, Rutger ter Borg <rutger(a)terborg.net> wrote: Hi Rutger, > [...]have a couple of questions. Currently a part of the semantics is > > sh.add_signal( SIGUSR1 ); > sh.async_wait( handler ); > > Wouldn't it be easier to be able to write > > sh.async_wait( SIGUSR1, handler ); this would work if you wait for only one signal unless ... > Alternatively, if catching multiple signals by one handler is required, > one > could think of something like > > sh.async_wait( sigusr1 | sigterm | sigabrt, handler ); ... this notion is supported. But this would require to redefine every signal (like sigusr1 for SIGUSR1)? Is this practically possible? I wonder how many differences there are between platforms and if this causes more maintenance effort? I also wonder what is more asio-like. If I look at the I/O objects of Boost.Asio it seems like they are always configured before an asynchronous operation is called. For example when using the deadline_timer expires_at() or expires_from_now() must be called before async_wait() is called. > sh.async_wait( boost::asio::posix::any_signal, handler ); Same answer as above. :) Apart from that I wonder how many developers would benefit from boost::asio::posix::any_signal. Are there so many applications which need to wait for all signals? > Does the signal ID belong in the signature of the handler function? Am I Yes, please see the test cases test/sync.cpp and test/async.cpp. Here's a simple example: ---------- #include "signal_handler.hpp" #include <boost/asio.hpp> #include <signal.h> void signal_handler(const boost::system::error_code &ec, int signal) { } int main() { boost::asio::io_service io_service; boost::asio::posix::signal_handler sh(io_service); sh.add_signal(SIGUSR1); sh.async_wait(signal_handler); io_service.run(); } ---------- > correct that support for real-time signals is missing at the moment? Not sure as I never used real-time signals. :) Looking up real-time signals the difference is merely prioritized delivery times and signal queues? If that's all real-time signals should be supported. The signal handler puts signals into a std::deque<int> object and doesn't merge signals either (when you call wait() or async_wait() the next signal is fetched from the queue). Boris

1 0

[ANN] CLI command line interface compiler for C++
by Boris Kolpackov 29 Oct '09

29 Oct '09

Hi, I am pleased to announce the first public release of CLI. CLI is an open-source (MIT license), cross-platform command line interface compiler for C++. It allows you to specify the options that your program supports, their types, and default values. For example: include <string>; class options { bool --help; std::string --name = "example"; unsigned int --level | -l = 5; }; This specification can then be automatically translated to C++ classes that implement parsing of the command line arguments and provide a convenient and type-safe interface for accessing the extracted data. For example: #include <string> class options { public: options (int argc, char** argv); options (int argc, char** argv, int& end); bool help () const; const std::string& name () const; unsigned int level () const; ... }; int main (int argc, char* argv[]) { options o (argc, argv); if (o.help ()) print_usage (); if (o.level () > 4) cerr << "name is " << o.name () << endl; ... } It is easy to start using CLI in your application since there are no external dependencies. You can compile your command line interface to C++ and simply add the generated files to your project's source code. For a five minute introduction to CLI, see the "Hello World" example in the CLI Getting Started Guide: http://www.codesynthesis.com/projects/cli/doc/guide/#2 More information, documentation, and source code distributions are available from the project's web page: http://www.codesynthesis.com/projects/cli/ Enjoy, Boris -- Boris Kolpackov, Code Synthesis Tools http://codesynthesis.com/~boris/blog Open-source XML data binding for C++: http://codesynthesis.com/products/xsd XML data binding for embedded systems: http://codesynthesis.com/products/xsde

1 0

[serialization] Serializing a reference
by Ben 29 Oct '09

29 Oct '09

Hello Boost Experts -- And now for my real question. Again, g++ 4.2.1, OS X 10.6.1, boost 1.40. I'm trying to follow the instructions in the document for serializing classes with reference members, which suggests I serialize them as pointers. First, a program which works, that uses pointers and not references: #include <iostream> #include <fstream> #include <boost/archive/binary_oarchive.hpp> #include <boost/archive/binary_iarchive.hpp> struct A { int v; template<class Ar> void serialize(Ar & ar, const unsigned int ver) { ar & v; } }; struct B { A *ap; B(A *ap_) : ap(ap_) {} template<class Ar> void serialize(Ar & ar, const unsigned int ver) {} }; template<class Ar> void save_construct_data(Ar & ar, const B * b, const unsigned int ver) { ar << b->ap; } template<class Ar> void load_construct_data(Ar & ar, B * b, const unsigned int ver) { A * ap_; ar >> ap_; ::new(b)B(ap_); } int main(int ac, char ** argv) { A a; a.v = 10; B * b1p; b1p = new B(&a); const char * fname = "test.bin"; { std::ofstream ofs(fname); boost::archive::binary_oarchive ar(ofs); ar << b1p; } B * b2p; { std::ifstream ifs(fname); boost::archive::binary_iarchive ar(ifs); ar >> b2p; } std::cout << b2p->ap->v << std::endl; return 0; } What I would really like to do is to modify this program so that class B has a reference to class A instead of a pointer. The documentation suggests I do the following: "This raises the question of how and where the objects being referred to are stored and how are they created. Also there is the question about references to polymorphic base classes. Basically, these are the same questions that arise regarding pointers. This is no surprise as references are really a special kind of pointer. We address these questions by serializing references as though they were pointers." The example given after this serializes the address of the referenced object, similar to the above. My translation of that code is: #include <iostream> #include <fstream> #include <boost/archive/binary_oarchive.hpp> #include <boost/archive/binary_iarchive.hpp> struct A { int v; template<class Ar> void serialize(Ar & ar, const unsigned int ver) { ar & v; } }; struct B { A &a; B(A &a_) : a(a_) {} template<class Ar> void serialize(Ar & ar, const unsigned int ver) {} }; template<class Ar> void save_construct_data(Ar & ar, const B * b, const unsigned int ver) { ar << (&(b->a)); } template<class Ar> void load_construct_data(Ar & ar, B * b, const unsigned int ver) { A * ap_; ar >> ap_; ::new(b)B(*ap_); } int main(int ac, char ** argv) { A a; a.v = 10; B * b1p; b1p = new B(a); const char * fname = "test.bin"; { std::ofstream ofs(fname); boost::archive::binary_oarchive ar(ofs); ar << b1p; } B * b2p; { std::ifstream ifs(fname); boost::archive::binary_iarchive ar(ifs); ar >> b2p; } std::cout << b2p->a.v << std::endl; return 0; } This however fails to compile, with the message: Compilation started at Fri Oct 23 15:25:29 make -k debug make all "CXX_FLAGS = -g -fno-inline -m64 -I. -I.. -I/opt/local/include -Wall -Wextra -Wpointer-arith -Wcast-align -Wwrite-strings -Wconversion -Woverloaded-virtual -Wno-sign-compare -Wno-unused -fno-nonansi-builtins" \ "LD_FLAGS = -g -m64" g++ -g -fno-inline -m64 -I. -I.. -I/opt/local/include -Wall -Wextra -Wpointer-arith -Wcast-align -Wwrite-strings -Wconversion -Woverloaded-virtual -Wno-sign-compare -Wno-unused -fno-nonansi-builtins -c test.cc -o test.o test.cc: In function 'void save_construct_data(Ar&, const B*, unsigned int) [with Ar = boost::archive::binary_oarchive]': /opt/local/include/boost/serialization/serialization.hpp:148: instantiated from 'void boost::serialization::save_construct_data_adl(Archive&, const T*, unsigned int) [with Archive = boost::archive::binary_oarchive, T = B]' /opt/local/include/boost/archive/detail/oserializer.hpp:179: instantiated from 'void boost::archive::detail::pointer_oserializer<Archive, T>::save_object_ptr(boost::archive::detail::basic_oarchive&, const void*) const [with Archive = boost::archive::binary_oarchive, T = B]' test.cc:60: instantiated from here test.cc:27: error: no match for 'operator<<' in 'ar << (A*)b->B::a' /opt/local/include/boost/archive/detail/interface_oarchive.hpp:63: note: candidates are: Archive& boost::archive::detail::interface_oarchive<Archive>::operator<<(T&) [with T = A*, Archive = boost::archive::binary_oarchive] make[1]: *** [test.o] Error 1 make[1]: Target `all' not remade because of errors. make: *** [debug] Error 2 Compilation exited abnormally with code 2 at Fri Oct 23 15:25:30 What am I doing wrong? Best regards, Ben

2 2

Boost deserialization of contained object fails when performed from a constructor, but succeeds otherwise.
by bhartsb 28 Oct '09

28 Oct '09

E.G.: ContainingClass::ContainingClass(){ pNA = new objectArray*[NUMBER]; //allocates ptrs ... pNA[ii] = new objectArray(SIZE);//allocates object array, and object array has a std::map "PatternsMap" ... pNA[ii]->load(pNA[ii], "../release/NA Data/NADataa descriptionNA0"); //fails pNA[ii]->PatternsMap.size(); //size = 0 } If I call the following lines of code after the constructor exits then all is well: pNA[ii]->load(pNA[ii], "../release/NA Data/NADataa descriptionNA0"); //succeeds pNA[ii]->PatternsMap.size();//size > 0 Any ideas? Note, that in the constructor example I verified that objectArray was constructed first. -- View this message in context: http://www.nabble.com/Boost-deserialization-of-contained-object-fails-when-… Sent from the Boost - Users mailing list archive at Nabble.com.

1 0

[Thread] io_service post is unsuccessful
by Dylan Klomparens 28 Oct '09

28 Oct '09

I'm trying to figure out why a call to boost::io_service::post might be failing. My program is multithreaded, and has a periodic "timing event" that is triggered. The timing event calls "Service.post(&OnSignal);" to execute a handler, while another thread runs the service. Using this design, I can post an event from any thread without worrying about explicit resource locking. My question is, why does my call to Service.post always fail? I know it is failing because the function that I post never gets called. There is not explicit return code or thrown exception to indicate that there is a problem. Below is an example of what I'm trying to do. Inside main(), there is a commented call to "Service.post(&OnSignal);". Uncommenting that line results in a successful post to the Service, which eventually calls OnSignal, (but only once, obviously). Why does that call work, but not the call in TimingSignalThread()? #include <iostream> #include <boost/asio.hpp> #include <boost/thread/thread.hpp> using namespace std; // This is the service responsible for queuing the events. boost::asio::io_service Service; // This is the function that should be periodically queued by the TimingSignalThread. void OnSignal() { cout << "Got timing signal"; } // This function runs in its own thread, and periodically posts OnSignal() to the Service. void TimingSignalThread() { boost::this_thread::disable_interruption di; // Run until interrupted by <enter>. while(!boost::this_thread::interruption_requested()) { cout << "."; boost::this_thread::sleep(boost::posix_time::millisec(500)); Service.post(&OnSignal); // This post is never successful. } } // This function runs in its own thread, and executes all posts. void ServiceRunner() { Service.run(); } int main() { boost::thread TimingThread(&TimingSignalThread); boost::thread ServiceThread(&ServiceRunner); // Why does 'post()' work here, but not in TimingSignalThread()? // Uncommenting the following line results in a single successful post to OnSignal. // Service.post(&OnSignal); cin.get(); // Press enter to end the program. TimingThread.interrupt(); TimingThread.join(); Service.stop(); ServiceThread.join(); cout << "Joined all threads." << endl; return 0; }

2 2

[Proto] Stuck turning a complex gramamr action to a primitive trasnform
by joel 28 Oct '09

28 Oct '09

I tried to turn a complex grammar transform : struct grammar : or_< ... ,bp::when< bp::nary_expr< bp::_, bp::vararg< grammar > > , bp::_default< grammar > ( _bp::functional::unpack_expr<bp::tag::function>( push_front( bp::_ , bp::_make_terminal ( some_type< bp::tag_of<bp::_> >() ) ) ) ) > into a single primitive transform but I end up stuck cause it seems some of those transform (make_terminal) don't follow the classic proto::result_of/proto namespace acces to compute it's return type and calling it. How should I handle these ? My intuition was that the transform oeprator() will call the equivalent function onto its expr parameters while its result struct compute the result_of by chaining the transform result_of results. Ultimately, I want this to be a tempalte trasnform that take some_type as a parameter : bp::when< bp::nary_expr< bp::_, bp::vararg< grammar > > , traversal<some_type>(bp) > Thanks in advance -- ___________________________________________ Joel Falcou - Assistant Professor PARALL Team - LRI - Universite Paris Sud XI Tel : (+33)1 69 15 66 35

2 3