- Boost-users - lists.boost.org

Compiler Error With boost::bind and boost::signals
by KERSAM 30 Jan '09

30 Jan '09

Hello. I have a compiler error when I try to use boost::bind and boost::signals. Here is the code: -------------------- #include<boost/bind.hpp> #include<boost/signals.hpp> class MyBoostTest { public: void testFunction(int x, int y) {} }; void doConnect() { boost::signal2<void, int, int> signal; signal.connect(boost::bind<void>(&MyBoostTest::testFunction, new MyBoostTest, _1)); } ----------------------------------- The compiler gives me the following error: c:\3rdparty\boost\boost\bind.hpp(289) : error C2064: term does not evaluate to a function taking 2 arguments class does not define an 'operator()' or a user defined conversion operator to a pointer-to-function or reference-to-function that takes appropriate number of arguments What am I doing wrong? Regards -- View this message in context: http://www.nabble.com/Compiler-Error-With-boost%3A%3Abind-and-boost%3A%3Asi… Sent from the Boost - Users mailing list archive at Nabble.com.

1 0

Re: [Boost-users] RBGL use with BGL minCut() function
by Gianni Loiacono 30 Jan '09

30 Jan '09

Thanks another time Mr. Sutton for the answer. This is my goal: "I have made a project that use efficiently BGL library. Now I have the necessity to use the Gomory-Hu algorithm......then I have searched on the net some source "boost compatible" that makes this algorithm ;)" But nothing, on the net there isn't this function.....I'm surprised because it is a fundamental algorithm of graph theory :o) Thanks a lot and sorry for my eng :) Bye.

1 0

Re: [Boost-users] [BGL] Bundled properties and property maps
by Andrew Sutton 30 Jan '09

30 Jan '09

On Tue, Jan 13, 2009 at 9:56 AM, Andrew Sutton <andrew.n.sutton(a)gmail.com>wrote: > Hi Andrew, apologies for writing directly to you, I just thought I'd try to >> get your attention this way since you hadn't yet replied to my last post on >> the above topic in the mailing list. >> > > Sorry about that, I've been swamped since new years. I'm going to bounce > this back to the list > > I would avoid declaring property maps as const. Somewhere in your posted > code you have: > > const property_map<...>::const_type map; // or something similar. > > For all property maps, map = get(...) is a valid expression, regardless of > whether your map is a ::type or ::const_type. By declaring it const, and > then instantiating a template with the const pmap, you're going to run into > problems - probably the problem you reported earlier. > > Andrew Sutton > andrew.n.sutton(a)gmail.com >

2 9

Boost 1.38.0 beta 2 available
by Beman Dawes 30 Jan '09

30 Jan '09

Boost 1.38.0 beta 2 available is available from SourceForge. http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041&… Please report any problems or comments to the users or developers mailing lists. ------------- Version 1.38.0 New Libraries * Flyweight: + Design pattern to manage large quantities of highly redundant objects, from Joaquín M López Muñoz. * ScopeExit: + Execute arbitrary code at scope exit, from Alexander Nasonov. * Swap: + Enhanced generic swap function, from Joseph Gauterin. Updated Libraries * Accumulators: + Add rolling_sum, rolling_count and rolling_mean accumulators. * Date_Time: + Added support for formatting and reading time durations longer than 24 hours with new formatter: %0. + Removed the testfrmwk.hpp file from the public include directory. + Fixed several bugs and compile errors. + For full details see the change history * Exception: + Improved and more customizable diagnostic_information output. * Hash: + boost/functional/detail/container_fwd.hpp has been moved to boost/detail/container_fwd.hpp. The current location is deprecated. + For more detail, see the library changelog. * Interprocess: + Updated documentation to show rvalue-references funcions instead of emulation functions. + More non-copyable classes are now movable. + Move-constructor and assignments now leave moved object in default-constructed state instead of just swapping contents. + Several bugfixes (#2391, #2431, #1390, #2570, #2528). * Intrusive: + New treap-based containers: treap, treap_set, treap_multiset. + Corrected compilation bug for Windows-based 64 bit compilers. + Corrected exception-safety bugs in container constructors. + Updated documentation to show rvalue-references funcions instead of emulation functions. * Math: + Added Johan Råde's optimised floating point classification routines. + Fixed code so that it compiles in GCC's -pedantic mode (bug report #1451). * Multi-index Containers: Some redundant type definitions have been deprecated. Consult the library release notes for further information. * Proto: + Fix problem with SFINAE of binary operators (Bug 2407). + Fix proto::call transform for callable transforms with >3 arguments. + result_of::value changed behavior for array-by-value terminals. + unpack_expr requires only Forward Sequences rather than Random Access Sequences. + Deprecate legacy undocumented BOOST_PROTO_DEFINE_(VARARG_)FUNCTION_TEMPLATE macros. + Add BOOST_PROTO_REPEAT and BOOST_PROTO_LOCAL_ITERATE macros to help with repetitive code generation + Support for nullary expressions with tag types other than proto::tag::terminal + Allow 0- and 1-argument variants of proto::or_ and proto::and_ * Regex: + Breaking change: empty expressions, and empty alternatives are now allowed when using the Perl regular expression syntax. This change has been added for Perl compatibility, when the new syntax_option_type no_empty_expressions is set then the old behaviour is preserved and empty expressions are prohibited. This is issue #1081. + Added support for Perl style ${n} expressions in format strings (issue #2556). + Added support for accessing the location of sub-expressions within the regular expression string (issue #2269). + Fixed compiler compatibility issues #2244, #2514, and #2458. * Unordered: + Use boost::swap. + Use a larger prime number list for selecting the number of buckets. + Use aligned storage to store the types. + Add support for C++0x initializer lists where they're available. + For more detail, see the library changelog. * Xpressive: + basic_regex gets nested syntax_option_flags and value_type typedef, for compatibility with std::basic_regex + Ported to Proto v4; Proto v2 at boost/xpressive/proto has been removed. + regex_error inherits from boost::exception Other Changes Experimental support for building Boost with CMake has been introduced in this version. For more details see the wiki, Discussion is taking place on the Boost-cmake mailing list. Compilers Tested Boost's primary test compilers are: * TODO * GCC 4.0.1 on OS X 10.4.10 and 10.5.2 on Intel and 10.4.9 on Power PC. * GCC 4.3.2 on Ubuntu Linux. * GCC 4.3.3 on Unstable Debian. * GCC 4.2.1 on HP-UX 64-bit. * HP C/aC++ B3910B A.06.17 on HP-UX 64-bit. * Visual C++ 7.1 SP1, 8.0 SP1 and 9.0 SP1 on Windows XP. Boost's additional test compilers include: * OS X: + GCC 4.0.1 on OS X 10.4.10 and 10.5.2 on Intel, OS X 10.4.9 on PowerPC + Intel 9.1, 10.0 on OS X 10.4.10 + Intel 10.1, 11.0 on OS X 10.5.2 * On Linux: + GCC 4.1.1, 4.2.1 on 64-bit Red Hat Enterprise Linux + GCC 4.1.2 on 64-bit Redhat Server 5.1 + GCC 3.4.3, GCC 4.0.1, GCC 4.2.4 and GCC 4.3.2 on Red Hat Enterprise Linux + GCC 4.3.2 with C++0x extensions + GCC 4.2.1 on OpenSuSE Linux + pgCC 8.0-0a 64-bit target on Red Hat Enterprise Linux + QLogic PathScale(TM) Compiler Suite: Version 3.1 on Red Hat Enterprise Linux * IBM XL C/C++ Enterprise Edition for AIX, V10.1.0.0, on AIX Version 5.3.0.40 * GCC 4.2.1 on FreeBSD 7. * GCC 4.2.1 on HP-UX Integrity * HP C/aC++ B3910B A.06.17 on HP-UX 64-bit. Acknowledgements TODO

1 0

BGL: Vertex or Vertex& ?
by Roger House 30 Jan '09

30 Jan '09

I've just started using the Boost Graph Library (which is proving to be a very nice tool) and I've encountered an issue: When vertex descriptors are passed as parameters, stored in vectors, etc., is it better to use Vertex&, or is Vertex alone okay. I've been assuming that a vertex descriptor is probably a pointer, so I've been using Vertex. But then is occurred to me that my assumption could be all wrong and I should be using Vertex&. Here are the Graph, Vertex, and Edge definitions I've been using: typedef adjacency_list < vecS, // edge container type vecS, // vertex container type undirectedS, VertexProperties, EdgeProperties, GraphProperties > Graph; typedef graph_traits<Graph>::vertex_descriptor Vertex; typedef graph_traits<Graph>::edge_descriptor Edge; Roger House

2 1

David M Garza is out of the office.
by David M Garza 30 Jan '09

30 Jan '09

I will be out of the office starting 01/30/2009 and will not return until 02/03/2009. I will respond to your message when I return.

1 0

[ASIO] random crashes
by Axel 30 Jan '09

30 Jan '09

Hello I m using ASIO library (from boost 1.35) in a network daemon (running on a Debian Etch system). The code structure is almost the same as the one described in the HTTP Server example (http://tenermerx.com/Asio/boost_asio_1_3_1/doc/html/boost_asio/examples.htm…) One io_service is used, async_accept() creates new "sessions" and so on. The daemon can run flawlessly for weeks (or only some hours), and crash randomly (segmentation fault). The "network" load isn't really high, every 5 minutes, a few megabytes of data (characters) are sent to the daemon. I didn't noticed any memory leaks or null pointers accesses. Among many crashes, I found 2 kind of crashes. Since core are dumped, I tried to debug it, but I don't know how to interpret the core result. The binary wasn't linked against debug libraries and I just can get debug data from the binary itself. Here's the gdb output on "bt full" command. The daemon has 4 threads, here s the gdb output of the one which causes the crash (I assume this is this one) First kind of crash : (only the relevant part is pasted, the output is huge). It seems to be related to the way I handle the timeout on a timer. In my daemon, the io_service thread may call close() function on the socket object when another thread may call cancel() on the socket object. Could this lead to a crash ? (I can post source code if needed) What is the best way to handle receive timeout *and* socket & timer close from another thread ? Thread 1 (process 27120): Program terminated with signal 11, Segmentation fault. #0 0xb7c7c024 in pthread_mutex_lock () from /lib/tls/i686/cmov/libpthread.so.0 No symbol table info available. #1 0xb7d5f0c6 in pthread_mutex_lock () from /lib/tls/i686/cmov/libc.so.6 No symbol table info available. #2 0x08060438 in boost::asio::detail::posix_mutex::lock (this=0x16) at /usr/include/boost/asio/detail/posix_mutex.hpp:71 error = 0 #3 0x08060559 in scoped_lock (this=0xb796807c, m=@0x16) at /usr/include/boost/asio/detail/scoped_lock.hpp:36 No locals. #4 0x08060ad0 in boost::asio::detail::epoll_reactor<false>::close_descriptor (this=0x2, descriptor=-1291829448) at /usr/include/boost/asio/detail/epoll_reactor.hpp:297 lock = {<boost::noncopyable_::noncopyable> = {<No data fields>}, mutex_ = @0x16, locked_ = 212} ev = {events = 6, data = {ptr = 0x25, fd = 37, u32 = 37, u64 = 8589934629}} #5 0x0809b189 in boost::asio::detail::reactive_socket_service<boost::asio::ip::tcp, boost::asio::detail::epoll_reactor<false> >::close (this=0xb3004358, impl=@0xb3037f1c, ec=@0xb7968128) at /usr/include/boost/asio/detail/reactive_socket_service.hpp:210 No locals. #6 0x0809b277 in boost::asio::stream_socket_service<boost::asio::ip::tcp>::close (this=0xb3000098, impl=@0xb3037f1c, ec=@0xb7968128) at /usr/include/boost/asio/stream_socket_service.hpp:145 No locals. #7 0x0809b2c5 in boost::asio::basic_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> >::close (this=0xb3037f18) at /usr/include/boost/asio/basic_socket.hpp:253 ec = {m_val = 0, m_cat = 0xb7c74c10} #8 0x08091129 in Session::handleTimeout (this=0xb3037f18, error=@0xb796821c) at Session.cc:80 Could someone bring me some explainations about this crash ? Second kind of crash : (I really have no idea from where could come the crash, the backtrace isn't very useful) (gdb) bt full #0 boost::asio::detail::scoped_lock<boost::asio::detail::posix_mutex>::unlock (this=0xb5631dac) at /usr/include/boost/asio/detail/scoped_lock.hpp:58 No locals. #1 0x00000000 in ?? () No symbol table info available. Could someone give me some advices about how to handle these crashes ? How could I get more data in backtrace ? Thanks in advance for your help. Regards

3 3

seg fault on windows with Boost threads, istringstream, mingw
by Tod Courtney 30 Jan '09

30 Jan '09

Hi I am working on a multithreaded application for linux and windows using Boost threads. For windows, we have been developing with MinGW G++ 3.4.4 (packaged in cygwin). My application uses a producer-consumer model where one thread produces tasks definitions and multiple worker threads complete the tasks. I discovered that our application runs fine on linux but crashes with a SIGSEGV fault on windows, at least when compiled with MinGW. When compiling the same application with MSVC it works fine. The SIGSEGV crash is not always in the exact same place in the code, but is very likely to occur -- it happens 99% of the time when there are 3 or more worker threads. The code runs fine if there is only 1 worker thread. If I try to use the debugger to get a stack trace, I find the stack is corrupted so I can not see the method or source code lines that caused the crash. I have tried boost 1.36 and 1.37. I have tried MinGW g++ 3.4.4 (from cygwin), 3.4.5 (main release) and 4.3 (alpha). I get the same results in all cases. I have added the -mthreads flag to the compile and link options for my application. I believe the problem is related to this code, which uses a istringstream to convert a string to a basic type (say a double): template <typename T> bool FromString(T &t,const std::string &s, std::ios_base &(*f)(std::ios_base &)=std::dec) { std::istringstream iss(s); return !(iss >> f >> t).fail(); } The istringstream object is local to the conversion function, and each istringstream is unique for each thread. So I wouldn't expect a thread-related problem, unless istringstream has internal state stored in static variables. However, if I replace that code with equivalent calls to C-lib functions like 'atof', the problem goes away. I have attached a test application, along with the makefile I use to build it, that demonstrates this problem. This test application fails for with a SIGSEGV when run with MinGW GCC 3.4.4 (from cygwin), MinGW 3.4.5 (current MinGW release) or MinGW GCC 4.3 alpha. It works fine when I compile with MSVC or Cygwin GCC (non-mingw version based on cygwin1.dll and pthreads). I hope there is a solution but at this point and hope for some help answering these questions: 1) Is there a multi-thread bug in the MinGW implementation istringstream? 2) Is there a problem with my build process? Am I missing a flag or using the wrong variation of a library? 3) Is this problem unique to my machine or reproducible by others? 4) Has anyone else encountered a similar issue? If you have experience with using Boost threads with MinGW I would love to hear any pointers or suggestions you can share. If you try this test application with MinGW G++ and it works I would love to know it. If multiple people can confirm this is a bug, I want to submit it to either the MinGW or Boost threads dev. teams. Thanks in advance for your help, Tod Courtney -- Tod Courtney Delcross Technologies LLC tcourtney(a)delcross.com, www.delcross.com (217) 363-3396 ext 103 mingw34: test.cpp c:\\MinGW\\bin\\g++ -mthreads -o mingw34 test.cpp -I c:\\boost\\boost_1_37_0 -L c:\\boost\\boost_1_37_0\\stage\lib -lboost_thread-mgw34-mt newmingw43: test.cpp c:\\mingw4\\bin\\g++ -mthreads -o newmingw43 test.cpp -I c:\\boost\\boost_1_37_0 -L c:\\boost\\boost_1_37_0\\stage\\lib -lboost_thread-mgw43-mt nocygwin: test.cpp /usr/bin/g++ -mthreads -o nocygwin test.cpp -I /cygdrive/c/boost/boost_1_37_0 -L /cygdrive/c/boost/boost_1_37_0/stage/lib -mno-cygwin -lboost_thread-mgw34-mt cygwin: test.cpp /usr/bin/g++ -o cygwin test.cpp -I /cygdrive/c/boost/boost_1_37_0 -L /cygdrive/c/boost/boost_1_37_0/stage/lib -lboost_thread_pthread-gcc34-mt-1_37 #include <string> #include <vector> #include "boost/bind.hpp" #include "boost/thread.hpp" #include "boost/thread/barrier.hpp" using namespace std; boost::mutex msgMutex; //////////////////////////////////////////////////////////////////////// /// threadsafe tracing method void msg(const std::string &str) { boost::mutex::scoped_lock lock(msgMutex); cout<<str<<endl; } //////////////////////////////////////////////////////////////////////// /// method run by each worker thread bool exec(std::vector<string> * vec) { char buff[256]; // wait here until all threads have been created msg(string("START THREAD: ")); // now do the work for(size_t n=0;n<vec->size();n++) { string val=(*vec)[n]; double d=0; d=atof(val.c_str()); // COMMENTING OUT THE NEXT TWO LINES AVOIDS THE SIGSEGV istringstream iss(val); iss>>d; sprintf(buff,"value=%lf",d); msg(string(buff)); } msg("EXEC DONE: "); return true; } //////////////////////////////////////////////////////////////////////// /// main method: parse inputs and create worker threads int main(int argc, char **argv) { int numThreads=0; if (argc==2) numThreads=atoi(argv[1]); else cout<<"USAGE: "<<argv[0]<<" <numthreads>"<<endl; boost::thread **worker; vector<string> **vec; worker=new boost::thread*[numThreads]; vec=new vector<string>*[numThreads]; for(int n=0;n<numThreads;n++) { vec[n]=new vector<string>; for(int m=0;m<10;m++) { ostringstream oss; oss<<n<<"."<<m; vec[n]->push_back(oss.str()); } worker[n]=new boost::thread(boost::bind(&exec,vec[n])); } // wait until all threads to end for(int n=0;n<numThreads;n++) { worker[n]->join(); delete worker[n]; delete vec[n]; } delete [] worker; delete [] vec; }

2 1

[serialization] Can access::destroy (please) be removed?
by Maarten Nieber 30 Jan '09

30 Jan '09

Hi, my compiler (Visual Studio 2003) gives an error in access.hpp when I try to serialize an object that has a protected destructor (see summarized compiler output below). If I comment out the call to delete in access::destroy, the compiler does no longer complain and my code seems to work. Is the destroy function (or: the delete call) really needed? Thanks!, Maarten MyClass::MyClass' : cannot access protected member declared in class 'MyClass' boost\archive\detail\iserializer.hpp(105) : see reference to function template instantiation 'void boost::serialization::access::destroy<T>(const T *)' being compiled

1 0

[boost][asio] deadline_timer doesn't delays - async_wait invokes handler at once
by tomasz jankowski 30 Jan '09

30 Jan '09

Hello, I would like to add timeout to my server which is based on "http server 3" example. But I don't know why but I can't force deadline_timer to work properly. deadline_timer doesn't delays invoking of handler. please look how I modified source code of connection::start() in "http server 3" example. I did it according to suggestion placed on http://lists.boost.org/Archives/boost/2007/04/120339.php Could someone tell me what I.m doing wrong? tom void set_result(boost::optional<boost::system::error_code>* a, boost::system::error_code b) { a->reset(b); } void connection::start() { boost::optional<boost::system::error_code> timer_result; boost::asio::deadline_timer timer(socket_.io_service(),boost::posix_time::seconds(5)); timer.async_wait(boost::bind(set_result, &timer_result, _1)); boost::optional<boost::system::error_code> read_result; socket_.async_read_some(boost::asio::buffer(buffer_), strand_.wrap( boost::bind(&connection::handle_read, shared_from_this(), boost::asio::placeholders::error, boost::asio::placeholders::bytes_transferred))); socket_.io_service().reset(); while (socket_.io_service().run_one()) { if (read_result){ timer.cancel(); }else if(timer_result) { socket_.cancel(); } } if (*read_result) { throw boost::system::system_error(*read_result); } } ---------------------------------------------------- Pierwszy w Polsce profesjonalny serwis o modelkach! Zobacz zdjęcia, video i piękne kobiety. - Kliknij: http://klik.wp.pl/?adr=http%3A%2F%2Fcorto.www.wp.pl%2Fas%2Falemodelki.html&…

2 2