- Boost-users - lists.boost.org

Re: [Boost-users] program option library segfaults for exception
by Neetu Garg 19 Mar '10

19 Mar '10

I did little more digging into the issue If I compile and link following sample on Linux dynamically using following command g++ -c -I. -I/usr/local/include/boost-1_38 -I/usr/include testprogramoptions.cpp -o testprogramoptions.o g++ testprogramoptions.o -static-libgcc -L/u/neetug/Projects/performance/perfstat_cluster/lib -lboost_program_options-gcc41-mt -lpthread -o testprogramoptions [root@perf-tools-7 src]# ./testprogramoptions --o ERROR unknown option o ERROR Error while parsing CLI options Exiting Here "--o" is unknown option ======================================================================= If I compile and link following sample on Linux statically using following command g++ -c -I. -I/usr/local/include/boost-1_38 -I/usr/include testprogramoptions.cpp -o testprogramoptions.o g++ testprogramoptions.o -static-libgcc -Wl,-Bstatic -L/u/neetug/Projects/performance/perfstat_cluster/lib -lboost_program_options-gcc41-mt -lpthread -o testprogramoptions [root@perf-tools-7 src]# ./testprogramoptions --o Aborted Here "--o" is unknown option ======================================================================== I am not sure why the behavior is different with different linking option why I am not getting exception for static linking. Really appreciate any help in this issue. Here in the test program #include <iostream> #include <boost/program_options.hpp> namespace boostOptions = boost::program_options; using namespace std; int main(int argCount, char* argList[]) { try { boostOptions::options_description commonOpt("Options (common)"); commonOpt.add_options() ("help,h", "Produce help message.") ("version,v", "Prints perfstat version, and supported ONTAP versions.") ; boostOptions::options_description runModeOpt("Options ('run' mode)"); runModeOpt.add_options() ("clusterinfo", boostOptions::value<string>(), "cluster IP.") ("sample-interval", boostOptions::value<int>(), "Specifies statit/sysstat frequency") ; boostOptions::positional_options_description posOption; posOption.add("clusterinfo", -1); boostOptions::options_description allOptDesc("Allowed options :"); allOptDesc.add(commonOpt).add(runModeOpt); boostOptions::variables_map varMap; boostOptions::store(boostOptions::command_line_parser(argCount, argList). options(allOptDesc).positional(posOption).run(), varMap); boostOptions::notify(varMap); } catch(std::exception &e) { cout << "ERROR " << e.what() << "\n"; cout << "ERROR " << "Error while parsing CLI options Exiting" << "\n"; exit(0); } catch(...) { cout << "ERROR 1 " << "\n"; cout << "ERROR 1 " << "Error while parsing CLI options Exiting" << "\n"; exit(0); } } Regards, NG ----- Original Message ---- From: Neetu Garg <garg_neetu(a)yahoo.com> To: boost-users(a)lists.boost.org Sent: Wed, March 17, 2010 1:17:07 PM Subject: program option library segfaults for exception Sorry for the duplicate post, I think my message posted under different conversation. Hi, I have application that is using boost program option library. If I provide unknown option via CLI it should throw exception. The library is statically linked on windows and Linux environment. It works fine on windows platform I do get exception for unknown CLI option. On Linux platform I get "segfault" in place of exception for unknown CLI option. It is s a multi-threaded application and it also uses boost thread library. Application does throw exception on Linux also if I link dynamically. I am using following flags to link the library statically: LDFLAGS= -fexceptions -static-libgcc -Wl,-static -L/usr/lib -lboost_program_options-gcc41-mt -lboost_filesystem-gcc41-mt -lboost_thread-gcc41-mt -lboost_system-gcc41-mt -lnet7ssh -lbotan -ltar -lz -lrt -lpthread I am using following version of gcc: # g++ --version g++ (GCC) 4.1.1 Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Here is the core dump for the segfault: (gdb) backtrace #0 __gnu_internal::get_global () at /usr/software/src/gcc-4.1.1/libstdc++-v3/libsupc++/eh_globals.cc:58 #1 0x082c0f67 in __cxa_get_globals () at /usr/software/src/gcc-4.1.1/libstdc++-v3/libsupc++/eh_globals.cc:71 #2 0x082c0b3f in __cxa_allocate_exception (thrown_size=32) at /usr/software/src/gcc-4.1.1/libstdc++-v3/libsupc++/eh_alloc.cc:154 #3 0x080a71f8 in boost::program_options::detail::cmdline::finish_option () #4 0x080a77eb in boost::program_options::detail::cmdline::run () #5 0x0806f3aa in boost::program_options::basic_command_line_parser<char>::run () #6 0x080660e9 in CLIHandler::collectCLIOptions () #7 0x0808a0d1 in perfstat::runPerfstat () #8 0x0808af3d in main () Current language: auto; currently c++ Appreciate your help Regards, NG

1 0

[Proto] Turnign grammar into primitive transform : _default is being naughty with me :(
by joel falcou 19 Mar '10

19 Mar '10

I'm polisihng some generic recursive descent grammar to evaluate various sort of expression that only differ on how nodes and leaf are treated. I was trying, once the grammar was set up using combo of transform to make a single primitive transform to speed up compile-time. Everythign worked until I hit a brick wall while trying to put the last non-generic part (the call to proto::_default) inside my own transform. Here is link to the working.cpp and not_working.cpp stand alone source file for inspection. test were done on 1.42 release. http://www.lri.fr/~falcou/tmp/working.cpp http://www.lri.fr/~falcou/tmp/not_working.cpp The error is : http://www.lri.fr/~falcou/tmp/errors.txt thanks for any pointer on this issue which, I think, is a stupid mistake on my side. -- ___________________________________________ Joel Falcou - Assistant Professor PARALL Team - LRI - Universite Paris Sud XI Tel : (+33)1 69 15 66 35

2 2

boost::asio destructor segfault?
by Sean McAllister 19 Mar '10

19 Mar '10

I've got a class that's using ASIO to run a simple server listening for command messages from a remote interface. It's got some private members to help with this (class abridged for shortness): class ClassifierContext { private: io_service ioService_; t_socket_shptr socket_; }; It runs it's event loop in it's own thread (started with boost::thread) // Hosts thread to run IO event loop void ClassifierContext::io_loop() { try { connect(); } catch (std::exception &e) { RERROR("Error connecting to site server -- %s", e.what()); } // Work object prevents run() from stopping when it runs out of work asio::io_service::work work(ioService_); ioService_.run(); } And it periodically sends data back along a single socket associated with the ioService and also has an asynchronous read pending to listen for command messages (I can post this code if needed, it's just a couple async_sends and an async_read) The problem I'm seeing comes when the destructor for the class is run: ClassifierContext::~ClassifierContext() { ioService_.stop(); } Periodically (every 20 times or so) I get a segfault when the destructor for ioService_ is called. A representative stack trace looks like this: #0 0x0921bfd6 in ?? () #1 0x08125877 in boost::asio::detail::reactor_op_queue<int>::destroy_operations ( this=0x8ec5f40) at opt/linux/include/boost/asio/detail/reactor_op_queue.hpp:268 #2 0x081274ad in boost::asio::detail::epoll_reactor<false>::shutdown_service ( this=0x8ec5ed8) at opt/linux/include/boost/asio/detail/epoll_reactor.hpp:119 #3 0x08127b3b in ~service_registry (this=0x8ec5958) at opt/linux/include/boost/asio/detail/service_registry.hpp:75 #4 0x08127c29 in ~io_service (this=0x8492360) at opt/linux/include/boost/asio/impl/io_service.ipp:62 #5 0x08117110 in ~ClassifierContext (this=0x8492360) at ClassifierContext.cpp:91 #6 0xb781cbb9 in exit () from /lib/tls/i686/cmov/libc.so.6 #7 0xb780477d in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #8 0x081079c1 in _start () at ../sysdeps/i386/elf/start.S:119 Has anyone seen a segfault like this before? It's intermittent so that tells me there's some kind of race condition. Any idea how I can work around it?

2 8

Compile under 32bits but not under 64bits
by Juanma Font 19 Mar '10

19 Mar '10

Hello ¡¡¡ Probed with boost 1.38 and 1.40 on linux ubuntu karmic Example: check64.cpp --------------- #include "check64.hpp" int main() { point2<int> png_size1(3,4); point2<int> png_size2; wxMessageBox( wxT("Reading png dimensions prueba.png "), wxT("Hello") ); // ok, compile into 32bits and 64bits png_size2=png_size1; // ok, compile into 32bits and 64bits png_read_dimensions( "prueba.png" ); //ERROR, THIS ONLY COMPILE WITH 32bits png_size1 = png_read_dimensions( "prueba.png" ); return 0; } ---------------------------------------- The error when try to compile with 64bits is: error: no match for ‘operator=’ in ‘png_size1 = boost::gil::png_read_dimensions(const char*)()’ Anybody knows what is happening ? The head file, check64.hpp is -------------------------- check64.hpp ------------- #ifndef CHECK64_HPP_INCLUDED #define CHECK64_HPP_INCLUDED #include <boost/gil/gil_all.hpp> #include <boost/gil/extension/io/png_io.hpp> #include <wx/wx.h> using namespace boost; using namespace boost::gil; using namespace std; #endif // CHECK64_HPP_INCLUDED --------------------------end of code -------------- Thank's a lot of

2 2

vc++ assertion error upon runtime
by hitesh dhiman 19 Mar '10

19 Mar '10

Hi all, I'm trying to gain access to functions that use pointers as arguments. I have written the wrapper file that converts the arguments into pointers. The compilation works successfully, but when i try to run the code from python, it gives an assertion error: Debug Assertion Failed! Expression: Vector subscript out of range Surprisingly, this error only occurs when a particular function is called, Until that point, the code works perfectly. Could someone guide me what to do?? -- Regards, Hitesh Dhiman Electrical Engineering National University of Singapore

1 0

scoped_lock lock&unlock
by weii 19 Mar '10

19 Mar '10

Dear all, I got a compiler(gcc 3.4.5) error while using boost.thread: ----------------------------------------------------------------------------- g++ -IC:\Program Files\boost\boost_1_40 -O0 -g3 -Wall -c -fmessage-length=0 -omain.o ..\main.cpp C:/Program Files/boost/boost_1_40/boost/thread/win32/basic_timed_mutex.hpp: In member function `bool boost::detail::basic_timed_mutex::timed_lock(const Duration&) [with Duration = bool]': C:/Program Files/boost/boost_1_40/boost/thread/locks.hpp:353: instantiated from `bool boost::unique_lock<Mutex>::timed_lock(const TimeDuration&) [with TimeDuration = bool, Mutex = boost::mutex]' C:/Program Files/boost/boost_1_40/boost/thread/locks.hpp:241: instantiated from `boost::unique_lock<Mutex>::unique_lock(Mutex&, const TimeDuration&) [with TimeDuration = bool, Mutex = boost::mutex]' ..\main.cpp:17: instantiated from here C:/Program Files/boost/boost_1_40/boost/thread/win32/basic_timed_mutex.hpp:118: error: no match for 'operator+' in 'boost::get_system_time() + timeout' C:/Program Files/boost/boost_1_40/boost/date_time/time.hpp:140: note: candidates are: T boost::date_time::base_time<T, time_system>::operator+(const typename time_system::date_duration_type&) const [with T = boost::posix_time::ptime, time_system = boost::posix_time::posix_time_system] C:/Program Files/boost/boost_1_40/boost/date_time/time.hpp:160: note: T boost::date_time::base_time<T, time_system>::operator+(const typename time_system::time_duration_type&) const [with T = boost::posix_time::ptime, time_system = boost::posix_time::posix_time_system] C:/Program Files/boost/boost_1_40/boost/operators.hpp:255: note: boost::date_time::date_duration<boost::gregorian::date_duration_rep> boost::operator+(const boost::date_time::date_duration<boost::gregorian::date_duration_rep>&, const boost::date_time::date_duration<boost::gregorian::date_duration_rep>&) C:/Program Files/boost/boost_1_40/boost/date_time/posix_time/date_duration_operators.hpp:76: note: boost::posix_time::ptime boost::posix_time::operator+(const boost::posix_time::ptime&, const boost::gregorian::years&) C:/Program Files/boost/boost_1_40/boost/date_time/posix_time/date_duration_operators.hpp:32: note: boost::posix_time::ptime boost::posix_time::operator+(const boost::posix_time::ptime&, const boost::gregorian::months&) C:/Program Files/boost/boost_1_40/boost/date_time/date_duration_types.hpp:245: note: boost::gregorian::date boost::date_time::operator+(const boost::gregorian::date&, const boost::date_time::years_duration<boost::gregorian::greg_durations_config>&) C:/Program Files/boost/boost_1_40/boost/date_time/date_duration_types.hpp:133: note: boost::gregorian::date boost::date_time::operator+(const boost::gregorian::date&, const boost::date_time::months_duration<boost::gregorian::greg_durations_config>&) Build error occurred, build is stopped ----------------------------------------------------------------------------------------------------------------------------- The following is my code: ----------------------------------------------------------------------------------------------------------------------------- #include <boost/thread/thread.hpp> #include <boost/thread/mutex.hpp> #include <boost/bind.hpp> #include <iostream> boost::mutex io_mutex; void count(int id) { boost::mutex::scoped_lock lock(io_mutex,false); for (int i = 0; i < 10; ++i) { lock.lock(); std::cout << id << ": " << i << std::endl; lock.unlock(); } } int main(int argc, char* argv[]) { boost::thread thrd1(count, 1); boost::thread thrd2(count, 2); thrd1.join(); thrd2.join(); return 0; } ----------------------------------------------------------------------------- I know I can just abandon the lock() and unlock() function since the constructor and destructor will do them for me. But I can't understand how this error occurs and why the compiler has something to do with basic_timed_mutex. Anyone can give me some clues? Thanks in advance.

1 1

[interprocess] Sharing data in a peer-to-peer fashion
by Brett Gmoser 19 Mar '10

19 Mar '10

Hello, I'm working on what seems to be a fairly interesting problem, and I'm looking for any interprocess experts to lend any advice. After reading all of the documentation for Interprocess, it seems that all of the examples work with a "one parent, many children" type model. The problem that I am having is that I am working with a "many children, no parent" model. My processes are spawned by the web server (and FastCGI), so there is no easy way to modify that code to manage the interprocess data. At least one instance of my program is meant to stay alive forever, so I'm not very concerned about deleting the interprocess data at any time. My problem however is the mutexes, and the stale locks that result if one of the processes crashes or exits abnormally. It seems that once an instance of my application crashes, no other instance may ever get a lock on the shared mutex, because the original process still holds a lock. I've thought of a few different ideas to solve this problem: * Using an interprocess shared_ptr for the mutex and data, with a custom deleter to remove all instances once the last application is exiting and the use count is zero. However this suffers from the same problem - it seems the use count is never decremented when the application exits abnormally (for example, kill -9, crash, or CTRL+C). * Using a "heart beat" type system to keep track of processes. My idea was to do something like this: Keep an interprocess associative array of process ID's mapped to last heartbeat time, with each process updating it's own heartbeat. At the same time, every other process (since there is no one parent process) must keep track of the heartbeats, and remove processes from the array which have not responded with a heartbeat in awhile. The problem is this - what about the mutex for the associative array? And the locks that another application might have on them? I wind up back at the point that I started at. The stale locks are destroyed if the mutex is deleted (via boost::interprocess::named_mutex::delete), and I can detect the stale lock pretty reliably with a timed try lock (wait 30 seconds or so to aquire the lock, if it can never be acquired then there is obviously a problem). But what of thread safety, since I now have to delete the lock and re-create it, where other processes might wind up doing the same thing? And what if those other processes are also trying to obtain a lock on the mutex at the same time I'm deleting and recreating it? Those are pretty much the only ideas I've had. Does anybody have anything better? Maybe some of you have tackled a similar problem? Thanks!

2 1

passing pointers from python
by hitesh dhiman 19 Mar '10

19 Mar '10

Hi all, i'm trying to wrap c++ functions that have pointer variables. The test example i'm using is shown below: int World::addition(int* a, int* b) { int z = *a + *b; return z; } Now, i defined it in my wrapper as : .def("addition", &World::addition) My code compiles, but when I try to execute it from python, i get this error: Python Argument types in World.Addition(World, int, int) did not match C++ signature: addition(class World {lvalue}, int* , int*) The problem is, how to get hold of a pointer in python? Or is there a workaround to define the function differently in the wrapper file? -- Regards, Hitesh Dhiman Electrical Engineering National University of Singapore

2 2

Initialising boost::interprocess::basic_string using std::string
by med ennemri 19 Mar '10

19 Mar '10

Hi all How to initialising boost::interprocess::basic_string using std::string; -- One God is Allah, all prophets are humans.

2 1

[boost-users][[proto] : Seeking advice on a DSL
by Manjunath Kudlur 19 Mar '10

19 Mar '10

Hello, I want to create a DSL where users are allowed to create "free" variables and then use them are parameters and local variables in their mini-program. For example, I want to have something like int_ a,b,c; Program(&a,b) [c = b*2, a = c] The parameter with the '&' prefix represents output, the ones without represent input. So, Program(&a, b)[...] should behave as a function object with prototype void foo(int&, const int), and I should be able to do the following : int ra; BOOST_AUTO(pr, Program(&a,b) [c = b*2, a = c]); pr(ra, 4); I am seeking some advice on implementing the "evaluator" for this language. In particular, where do I store the values corresponding to these free variables? To draw parallels with Boost.Phoenix, in phoenix, arg1, arg2.. etc are uniquely typed, and the evaluator just creates a fusion::vector<...> with the values passed in, and argN evaluation just returns fusion::at_c<N>(env.args()). In my case, I could create a unique ID for each free variable, and create a std::map from ID to value, and use that as the environment. Evaluator of the free variables can then look up that map to find values. But I consider this too heavy weight. In contrast, the fusion::vector<...> would incur very little overhead during run time. I will be grateful for any suggestions on other ways to implement the evaluator. Thanks in advance, Manjunath

2 6