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

Unable to figure out how to get zlib support in iostreams on windows
by cheesy4poofs 10 Feb '06

10 Feb '06

Hi, I've posted this on the boost build forums, but never got a response, so I'm hoping someone in this group can help me. I've spent several days banging my head with iostream zlib support on windows. For the life of me, I cannot figure out how to get this to compile. This is on a windows XP machine with Microsoft VS 2003. I've installed the zlib source at C:\dev\zlib and set the appropriate command line arguments (I believe anyway) to point to it. However, it continues to give me an error of "unknown dependent target <@boost!libs!iostreams!build>libboost_zlib.lib" If I remove the zlib command line arguments, the boost library builds fine. Can anyone please explain what I'm doing wrong? I'm sure it is something simple, but I cannot figure it out. I looked at the jam file regarding this and it seems to indicate that it will compile zlib automatically. But apparently that isn't happening. The complete output from the command window follows. Thanks in advance for any help! Scott bjam "-sTOOLS=vc-7_1" "-sNO_COMPRESSION=0" "-sNO_ZLIB=0" "-sZLIB_SOURCE=C:\Dev\zlib" "-sZLIB_INCLUDE=C:\Dev\zlib" stage ****************************************************** Building Boost.Iostreams with bzip2 support disabled. To enable bzip2, consult the Boost.Iostreams documentation ****************************************************** --------------------------------------------------------------------- *** If you don't need Boost.Python, you can ignore this section *** *** pass --without-python to suppress this message in the future *** skipping Boost.Python library build due to missing or incorrect configuration couldn't find Python.h in "c:/Python24/include" You can configure the location of your python installation by setting: PYTHON_VERSION - The 2-part python Major.Minor version number (e.g. "2.2", NOT "2.2.1") - currently "2.4" PYTHON_ROOT - automatically configured from PYTHON_VERSION if not otherwise set ; currently "c:/Python24" The following are automatically configured from PYTHON_ROOT if not otherwise set: PYTHON_LIB_PATH - path to Python library object; currently "c:/Python24/libs" --------------------------------------------------------------------- Building Boost.Regex with the optional Unicode/ICU support disabled. Please refer to the Boost.Regex documentation for more information (and if you don't know what ICU is then you probably don't need it). unknown dependent target <@boost!libs!iostreams!build>libboost_zlib.lib

3 2

Re: [Boost-users] [Serialization]Working without RTTI
by RIVASSEAU Jean Noel 10 Feb '06

10 Feb '06

I already pointed this out to Robert, the correct use is on the cpp file, not the documentation. I am also using no RTTI, for me it works fine except that I have to do all sort of strange things to get the thing to link correctly without multiple definitions. Jean-Noël -----Message d'origine----- De : boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] De la part de Alexandre Gacon Envoyé : vendredi 10 février 2006 10:11 À : boost-users(a)lists.boost.org Objet : Re: [Boost-users] [Serialization]Working without RTTI I looked at the test_no_rtti.cpp and I have a question: In the cpp file, the macro BOOST_CLASS_TYPE_INFO is used like this: BOOST_CLASS_TYPE_INFO( derived_base, extended_type_info_no_rtti<derived_base> ) But in the documentation, the macro is used like that: BOOST_CLASS_TYPE_INFO( derived_base, extended_type_info_no_rtti<base_class> ) What is the good use of the macro ? Thank you Alexandre Gacon -----Message d'origine----- De : boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] De la part de Robert Ramey Envoyé : jeudi 9 février 2006 16:17 À : boost-users(a)lists.boost.org Objet : Re: [Boost-users] [Serialization]Working without RTTI I've included that facility and a test which demonstrates it. test_no_rtti demonstrates how it can be used with a type_info facility which uses the string associated with the type via BOOST_CLASS_EXPORT. Other than that it hasn't been really tested/explored extensively. After doing all this, it occurred to me that it RTTI would still be required to serialize the std::vector etc. This could be worked around by some combination of the above a) implemented BOOST_CLASS_EXPORT for those serializations in the library b) making a custom extended_type_info class which uses some other yet to be determined method. c) avoiding serialization of types not exported via pointers. That is, only types serialized via pointers required RTTI. (at least that's the intention - better test this!!) Robert Ramey Alexandre Gacon wrote: > Hi, > > I would like to use the serialization library inside one of my project > which do not use the RTTI. I produce a first version using > boost::serialization::extended_type_info to produce the key associated > to the class. > > Is it possible to use my own keys instead of the extended_type_info > class to serialize my classes ? > > Thank you, > > Alexandre Gacon > Project Manager _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

2 1

Bug report : incorrect documentation for biconnected_components
by Jean-Noël Monette 10 Feb '06

10 Feb '06

Hello, The documentation given in this page : http://www.boost.org/libs/graph/doc/biconnected_components.html is incompleet. The function signatures don't match the functions found in the file biconnected_components.hpp. The VertexIndexMap index_map parameter was omitted from the declarations at the beginning of the doc page. It should be added for users of listS. Jean-Noël Monette

1 0

[Serialization]Working without RTTI
by Alexandre Gacon 10 Feb '06

10 Feb '06

Hi, I would like to use the serialization library inside one of my project which do not use the RTTI. I produce a first version using boost::serialization::extended_type_info to produce the key associated to the class. Is it possible to use my own keys instead of the extended_type_info class to serialize my classes ? Thank you, Alexandre Gacon Project Manager

2 2

Re: [Boost-users] progress_timer writes two newlines?
by Daniel Lidström 10 Feb '06

10 Feb '06

Daniel Lidström scribbled: > Hello! > > Why does boost::progress_timer write two newlines on destruction? One > would suffice for me. Another thing about progress_timer: Why is the only option to output seconds? I'd like to be able to use my own formatter, so that I can have the output in HH:MM:SS.mmm for example: boost::progress_timer timer(cout, hhmmssmmm_formatter()); Hälsningar, Daniel

2 1

multiple implicit constructors (MPL?)
by Cory Nelson 10 Feb '06

10 Feb '06

Hello, I have a class, large_integer<BaseT>. I build 256bit integers by doing: typedef large_integer<unsigned long long> uint128; typedef large_integer<uint128> uint256; Unfortunately C++ only seems to allow one implicit conversion, so I'm unable to do uint256 a = 0, and have to do uint256 a = uint128(0); instead. I'm able to get around one of these by having a constructor which takes the base type, but that only gets me one free conversion, meaning a uint512 has the same issue. Is there a way around this (I'm guessing MPL would be my best bet?)? -- Cory Nelson http://www.int64.org

1 0

[thread] Mysterious deadlock
by David Greene 10 Feb '06

10 Feb '06

I have this simple testcase (below) which runs into deadlock (full run trace after the testcase): ... [Producer] Producer generated data 28 [Producer] push(): about to lock [Producer] push(): locked [Producer] push(): about to unlock [Producer] Producer generated data 29 [Producer] push(): about to lock [Producer] push(): locked [Consumer] Signaled for data [Consumer] empty(): about to lock <<DEADLOCK>> The call to empty() by Consumer is after the first time it is woken up from full_condition. So the deadlock occurs right when the consumer first attempts to grab some data. Is there something I'm not understanding about how mutexes and locks work in Boost.Thread? I feel like I'm missing something obvious. This comes out of a larger and more complicated program but I was able to isolate the mysterious (to me) behavior I'm seeing. I used to use LOG for debugging but I thought there might be some interaction between the queue mutex locks and the print mutex locks so I switched to the non-locking LOG_NOLCK but observed no change in behavior. Any help is greatly appreciated. -Dave --------------------------------- Testcase #include <iostream> #include <queue> #include <map> #include <string> #include <boost/thread.hpp> #include <boost/thread/recursive_mutex.hpp> #include <boost/thread/condition.hpp> #include <boost/bind.hpp> #include <pthread.h> typedef boost::recursive_mutex mutex_type; typedef mutex_type::scoped_lock lock_type; // Atomic prints mutex_type print_mutex; mutex_type print_map_mutex; // For print/debug purposes typedef std::map<pthread_t, std::string> thread_map_type; thread_map_type thread_map; template<typename T> void register_thread_id(const T &entity) { lock_type lock(print_map_mutex); std::cout << "Registering " << pthread_self() << " to " << entity.name() << std::endl; thread_map[pthread_self()] = entity.name(); } #define LOG(msg) \ { \ lock_type lock(print_mutex); \ std::cout << "[" << thread_map[pthread_self()] \ << "] " << msg << std::endl; \ } #define LOG_NOLCK(msg) \ { \ std::cout << "[" << thread_map[pthread_self()] \ << "] " << msg << std::endl; \ } // Synchronize start (make sure all registered) mutex_type go_mutex; boost::condition go_condition; bool ready = false; class Consumer { private: boost::thread thread; std::queue<int> queue; typedef boost::recursive_mutex mutex_type; typedef mutex_type::scoped_lock lock_type; mutable mutex_type mutex; mutable mutex_type full_mutex; mutable boost::condition full_condition; void wait_until_ready(void) const { ::lock_type lock(go_mutex); while(!ready) { go_condition.wait(lock); } LOG_NOLCK("go!"); }; void wait_for_data(void) const { lock_type lock(full_mutex); while(empty()) { LOG_NOLCK("Waiting for data"); full_condition.wait(lock); LOG_NOLCK("Signaled for data"); } LOG_NOLCK("Wakeup for data"); }; void event_loop(void) { register_thread_id(*this); wait_until_ready(); while(true) { wait_for_data(); LOG_NOLCK("Consumer received data " << top()); pop(); } }; public: Consumer(void) : thread(boost::bind(&Consumer::event_loop, this)) {}; std::string name(void) const { return("Consumer"); }; void push(int val) { LOG_NOLCK("push(): about to lock"); { lock_type lock(mutex); LOG_NOLCK("push(): locked"); queue.push(val); lock_type full_lock(full_mutex); LOG_NOLCK("push(): about to unlock"); } full_condition.notify_all(); }; int top(void) const { LOG_NOLCK("top(): about to lock"); lock_type lock(mutex); LOG_NOLCK("top(): locked"); int item = queue.front(); LOG_NOLCK("top(): about to unlock"); return(item); }; void pop(void) { LOG_NOLCK("pop(): about to lock"); lock_type lock(mutex); LOG_NOLCK("pop(): locked"); queue.pop(); LOG_NOLCK("pop(): about to unlock"); }; bool empty (void) const { LOG_NOLCK("empty(): about to lock"); lock_type lock(mutex); LOG_NOLCK("empty(): locked"); bool val = queue.empty(); LOG_NOLCK("empty(): about to unlock"); return(val); }; }; class Producer { private: boost::thread thread; void wait_until_ready(void) const { lock_type lock(go_mutex); while(!ready) { go_condition.wait(lock); } LOG_NOLCK("go!"); }; void event_loop(void) { int i = 0; register_thread_id(*this); wait_until_ready(); while(true) { LOG_NOLCK("Producer generated data " << i); consumer->push(i); ++i; }; }; Consumer *consumer; public: Producer(Consumer *c) : consumer(c), thread(boost::bind(&Producer::event_loop, this)) {}; std::string name(void) const { return("Producer"); }; }; void go(void) { // Wait until everyone arrives lock_type lock(go_mutex); ready = true; // Notify everyone go_condition.notify_all(); } int main(void) { Consumer c; Producer p(&c); go(); while(true); return(0); } ----------------- Ouput Trace [Consumer] empty(): about to unlock [Consumer] Waiting for data Registering 48958384 to Producer [Producer] go! [Producer] Producer generated data 0 [Producer] push(): about to lock [Producer] push(): locked [Producer] push(): about to unlock [Producer] Producer generated data 1 [Producer] push(): about to lock [Producer] push(): locked [Producer] push(): about to unlock [Producer] Producer generated data 2 [Producer] push(): about to lock [Producer] push(): locked [Producer] push(): about to unlock [Producer] Producer generated data 3 [Producer] push(): about to lock [Producer] push(): locked [Producer] push(): about to unlock [Producer] Producer generated data 4 [Producer] push(): about to lock [Producer] push(): locked [Producer] push(): about to unlock [Producer] Producer generated data 5 [Producer] push(): about to lock [Producer] push(): locked [Producer] push(): about to unlock [Producer] Producer generated data 6 [Producer] push(): about to lock [Producer] push(): locked [Producer] push(): about to unlock [Producer] Producer generated data 7 [Producer] push(): about to lock [Producer] push(): locked [Producer] push(): about to unlock [Producer] Producer generated data 8 [Producer] push(): about to lock [Producer] push(): locked [Producer] push(): about to unlock [Producer] Producer generated data 9 [Producer] push(): about to lock [Producer] push(): locked [Producer] push(): about to unlock [Producer] Producer generated data 10 [Producer] push(): about to lock [Producer] push(): locked [Producer] push(): about to unlock [Producer] Producer generated data 11 [Producer] push(): about to lock [Producer] push(): locked [Producer] push(): about to unlock [Producer] Producer generated data 12 [Producer] push(): about to lock [Producer] push(): locked [Producer] push(): about to unlock [Producer] Producer generated data 13 [Producer] push(): about to lock [Producer] push(): locked [Producer] push(): about to unlock [Producer] Producer generated data 14 [Producer] push(): about to lock [Producer] push(): locked [Producer] push(): about to unlock [Producer] Producer generated data 15 [Producer] push(): about to lock [Producer] push(): locked [Producer] push(): about to unlock [Producer] Producer generated data 16 [Producer] push(): about to lock [Producer] push(): locked [Producer] push(): about to unlock [Producer] Producer generated data 17 [Producer] push(): about to lock [Producer] push(): locked [Producer] push(): about to unlock [Producer] Producer generated data 18 [Producer] push(): about to lock [Producer] push(): locked [Producer] push(): about to unlock [Producer] Producer generated data 19 [Producer] push(): about to lock [Producer] push(): locked [Producer] push(): about to unlock [Producer] Producer generated data 20 [Producer] push(): about to lock [Producer] push(): locked [Producer] push(): about to unlock [Producer] Producer generated data 21 [Producer] push(): about to lock [Producer] push(): locked [Producer] push(): about to unlock [Producer] Producer generated data 22 [Producer] push(): about to lock [Producer] push(): locked [Producer] push(): about to unlock [Producer] Producer generated data 23 [Producer] push(): about to lock [Producer] push(): locked [Producer] push(): about to unlock [Producer] Producer generated data 24 [Producer] push(): about to lock [Producer] push(): locked [Producer] push(): about to unlock [Producer] Producer generated data 25 [Producer] push(): about to lock [Producer] push(): locked [Producer] push(): about to unlock [Producer] Producer generated data 26 [Producer] push(): about to lock [Producer] push(): locked [Producer] push(): about to unlock [Producer] Producer generated data 27 [Producer] push(): about to lock [Producer] push(): locked [Producer] push(): about to unlock [Producer] Producer generated data 28 [Producer] push(): about to lock [Producer] push(): locked [Producer] push(): about to unlock [Producer] Producer generated data 29 [Producer] push(): about to lock [Producer] push(): locked [Consumer] Signaled for data [Consumer] empty(): about to lock <<DEADLOCK>>

4 5

unit test framework problems
by Niklas Wiberg 09 Feb '06

09 Feb '06

Hi, I'm having problems with the unit test framework when I try to run it in release mode. My compiler is VC++ 6 sp6. The unit test executable I'm building is "Using MFC as a shared DLL" and is set to use the "Multithreaded DLL" runtime library. The test subject code that is linked to this app is built with the same settings. I'm linking with libboost_unit_test_framework-vc6-mt-1_33.lib. The problem is that when the unit test starts to execute it fails with an access violation. In debug build it works fine. I enabled some debug info in the release build and found that what seems to be happening is a deallocation of "invalid" heap memory, which I'm guessing could be a result of different runtime libs being used. The stack trace at the point of the crash is included below. Has anyone had the same kind of problem and perhaps found a solution? Best regards, Niklas Wiberg NTDLL! 7c901230() NTDLL! 7c96cd80() NTDLL! 7c960af8() KERNEL32! 7c85e7af() _CrtIsValidHeapPointer(const void * 0x003b2418) line 1697 _free_dbg_lk(void * 0x003b2418, int 1) line 1044 + 9 bytes _free_dbg(void * 0x003b2418, int 1) line 1001 + 13 bytes free(void * 0x003b2418) line 956 + 11 bytes operator delete(void * 0x003b2418) line 7 + 10 bytes std::allocator<char>::deallocate(void * 0x003b2418, unsigned int 33) line 64 + 16 bytes std::basic_string<char,std::char_traits<char>,std::allocator<char> >::_Tidy(unsigned char 1) line 592 std::basic_string<char,std::char_traits<char>,std::allocator<char> >::~basic_string<char,std::char_traits<char>,std::allocator<char> >() line 59 + 17 bytes boost::filesystem::path::m_path_append(const std::basic_string<char,std::char_traits<char>,std::allocator<char> > & {0x0032f9f1 "D:\dev\UnitTest"}, unsigned char (const std::basic_string<char,std::char_traits<char>,std::allocator<char> > &)* 0x0054f9b3 boost::filesystem::native(const std::basic_string<char,std::char_traits<char>,std::allocator<char> > &)) line 351 boost::filesystem::path::path(const char * 0x0032f988, unsigned char (const std::basic_string<char,std::char_traits<char>,std::allocator<char> > &)* 0x0054f9b3 boost::filesystem::native(const std::basic_string<char,std::char_traits<char>,std::allocator<char> > &)) line 220 + 37 bytes boost::filesystem::current_path() line 803 + 22 bytes boost::filesystem::initial_path() line 810 + 28 bytes init_unit_test_suite(int 1, char * * 0x003b2da0) line 19 + 5 bytes UNITTEST! boost::unit_test::framework::init(int,char * * const) + 201 bytes UNITTEST! main + 54 bytes UNITTEST! mainCRTStartup + 227 bytes KERNEL32! 7c816d4f()

2 3

[iostreams] Hang when constructing an xml_iarchive with non-existent source
by Paul Giaccone 09 Feb '06

09 Feb '06

I have a function that uses a chain of filters that I am using to read encrypted, bzipped data from file. It is working fine. However, I have just discovered that if I call my function with a file that does not exist, the code hangs in the constructor for xml_iarchive. Of course, I have since edited my code to trap non-existent files before the code gets that far, but I am surprised that: * is_complete() returns true when the source is a non-existent file * the constructor for xml_iarchive hangs when it is given a stream that has a non-existent file as its source Is this correct behaviour or a bug? Of course, it is the programmer's responsibility to ensure the source exists, but a hang rather than an exception seems suggests to me that something has been overlooked in the library. The (edited) function exhibiting this behaviour is given below. I am using gcc 3.2.3 and Boost 1.33.1. Paul void load(const std::string& filename) { //my revised tests "filename" here and bails out if the file does not exist try { boost::iostreams::filtering_istream in; in.push(boost::iostreams::bzip2_decompressor()); in.push(MyInputEncryptionFilter()); in.push(boost::iostreams::bzip2_decompressor()); in.push(boost::iostreams::file_source(filename, BOOST_IOS::in | BOOST_IOS::binary)); if (!in.is_complete()) { std::cerr << "Error creating filtering input stream" << std::endl; return; } boost::archive::xml_iarchive input_archive(in); //deserialise file here return; } //various catches removed }

2 3

[bgl]
by Marcio Paim de Aquino 09 Feb '06

09 Feb '06

Hi, I'm trying to compile this example http://www.boost.org/libs/graph/example/johnson-eg.cpp. I have the following error from VC++ 6 SP2: --------------------Configuration: johnson-eg - Win32 Debug-------------------- Compiling... johnson-eg.cpp c:\arquivos de programas\microsoft visual studio\vc98\include\boost\graph\graph_concepts.hpp(479) : error C2664: 'const_constraints' : cannot convert parameter 1 from 'int [5][5]' to 'const int (&)[5][5]' Reason: cannot convert from 'int [5][5]' to 'const int [5][5]' There is no context in which this conversion is possible c:\arquivos de programas\microsoft visual studio\vc98\include\boost\graph\graph_concepts.hpp(477) : while compiling class-template member function 'void __thiscall boost::BasicMatrixConcept<int [5][5],unsigned int,int>::constraints(void)' Error executing cl.exe. johnson-eg.exe - 1 error(s), 0 warning(s) Does anyone know what's wrong? Regards Marcio Paim

2 1