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

[Boost 1.33.1].[64-bit]
by Prashant Thakre 23 Jan '07

23 Jan '07

Hi, I am trying to get 64-bit build of Boost 1.33.1 on following platforms: 1.Solaris 10 - Sun Studio 11 - Sparc. URL's listed below helped me to build some if not all. Patch -- http://blogs.sun.com/sga/entry/boost_1_33_1 Instruction for passing the relevant options to bjam -- http://blogs.sun.com/sga/category/Boost 2.HP-UX 11.23 - aCC A.06.02 - Itanium. How do I pass "+DD64" option to the compiler and the linker for 64-bit build. 3.AIX 5.3 - xlC/C++ 8.0 - PowerPC. Correct way to pass "-q64" option to the compiler and the linker. I do not really want to use the environment variable OBJECT_MODE. -- regards, Prashant Thakre

3 7

gdb and Invalid Address specified to RtlFreeHeap
by gelbeiche 23 Jan '07

23 Jan '07

Hi, I have an C++ application that uses the Oracle OCI libraries(oci.dll), which itself has references to msvcr71.dll. I compiled the application with gcc 3.4.2 under MinGW and for runtime usage I downloaded/installed the desired msvcr71.dll. From "installed.ini": [components] runtime=mingw-runtime-3.11.tar.gz w32api=w32api-3.8.tar.gz ... The program crashed at exit with the following error message in a dialog window: Microsoft Visual C++ Runtime Library Runtime Error ! abnormal program termination Because I want debug the error I installed gdb 5.2.1. When I run the program in gdb I get the following message: Program received signal SIGTRAP. Trace/breakpoint trap. ... warning: HEAP[...] warning: Invalid Address specified to RtlFreeHeap(230000, 246950) In the backtrace I see that it happens in OCIInitialize. So I suppose it has something to do with the oci.dll and msvcr71.dll. But I'm able to run the application outside the debugger and beside the crash at exit it is working. How can I debug my application ? My OS is Windows2000. Thomas -- http://www.randspringer.de

2 1

typesafe typedef that is not implicitly convertible
by pwm 23 Jan '07

23 Jan '07

I am unable to find it now, but I thought I saw that there is a boost way to define a typedef using a unique class that cannot be implicitly converted to another type. Thus, typedef int Foo; void bar( Foo a ); would compile only with bar( Foo(3) ) not bar(3) Is this capability in Boost 1.33 or am I hallucinating? Thanks, Phil

3 4

Re: [Boost-users] [general question] on threading anddoublecheckedlocking pattern
by Sohail Somani 23 Jan '07

23 Jan '07

Actually, its not so much wrong as it is "working currently but will probably break at some stage". Apparently, since Solaris always runs in "total storage ordering" mode, their implementation of pthread_once is correct for those hardware platforms. Just thought I'd clarify that. > -----Original Message----- > From: Sohail Somani > Sent: Monday, January 22, 2007 7:25 PM > To: 'boost-users(a)lists.boost.org' > Subject: RE: [Boost-users] [general question] on threading > anddoublecheckedlocking pattern > > Oopsie: > > http://bugs.opensolaris.org/view_bug.do?bug_id=6513516 > > So even the smart guys get it wrong. > > > -----Original Message----- > > From: boost-users-bounces(a)lists.boost.org > > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > > Sohail Somani > > Sent: Monday, January 22, 2007 5:12 PM > > To: boost-users(a)lists.boost.org > > Subject: Re: [Boost-users] [general question] on threading > > anddoublecheckedlocking pattern >

3 2

Re: [Boost-users] [general question] on threading anddoublecheckedlocking pattern
by Sohail Somani 23 Jan '07

23 Jan '07

Oopsie: http://bugs.opensolaris.org/view_bug.do?bug_id=6513516 So even the smart guys get it wrong. > -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Sohail Somani > Sent: Monday, January 22, 2007 5:12 PM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] [general question] on threading > anddoublecheckedlocking pattern

2 1

[multiindex] key extractor as free function - how?
by Markus Werle 23 Jan '07

23 Jan '07

Hi! I read from the docs that we can define key extractors to be one of - identity - member - mem_fun - composite_key Is it possible to use a free function as key extractor in the same way as the ones listed above and can you give an example of this? reagrds, Markus

3 6

Where to get boost 1.32 for solaris c++
by Victor Cheng 23 Jan '07

23 Jan '07

It seems that sun c++ has problems compiling boost 1.33.1 and the most compatible version is 1.32, but I could not find it any where on www.boost.org. It's probably in the cvs repository, but can't find the tag for 1.32. Is there a place where I can download this version?

2 1

[multiindex] combination with boost::tuple
by Markus Werle 23 Jan '07

23 Jan '07

Hi! I'd like to use boost::tuple in a list-replacing multiindex and use the first entry in the tuple as key. The following fails to compile. Could you please provide a correction? #include <boost/tuple/tuple.hpp> #include <boost/multi_index_container.hpp> #include <boost/multi_index/sequenced_index.hpp> #include <boost/multi_index/key_extractors.hpp> namespace bm = ::boost::multi_index; class C { typedef boost::tuple<std::string, std::string> data_t; template <typename T> struct mutable_value { mutable_value(const T& t):t(t){} operator T&()const{return t;} private: mutable T t; }; typedef bm::multi_index_container <mutable_value<data_t>, bm::indexed_by <bm::sequenced<>, bm::ordered_unique <bm::mem_fun<data_t, std::string, &data_t::get<0> > > > > storage_t; storage_t storage_; }; int main() { C c; }

2 4

compiling boost using codewarrior for windows
by Jean-Marc 23 Jan '07

23 Jan '07

when compiling boost ( the cvs version ) with metrowerks codewarrior for windows, I get a huge amount of errors. Is this (great !) compiler supported by boost ? Many thanks for your help Regards JM

1 0

[pool] fixed-size allocation pool
by Michael Marcin 23 Jan '07

23 Jan '07

I was wondering if I could use boost::pool for a fixed-sized object pool and return NULL if it tries to construct more than the maximum. Reading http://www.boost.org/libs/pool/doc/implementation/object_pool.html it seems like I could if I set_next_size(0) but it explicitly says I should not do that. Is there a reason to not support this behavior or is it supported in some other way/library? Thanks, Michael Marcin

1 0

Re: [Boost-users] [general question] on threading and doublecheckedlocking pattern
by Sohail Somani 23 Jan '07

23 Jan '07

It definitely is. But if you could find a way to make it better, even with complicated and platform-dependent code, and then wrap it up into something usable, have it tested and peer-reviewed, and placed somewhere we could all use it, it would still be useful. -------------- Sure -------------- P.S. In this particular case, I don't think you can get better than: - a read barrier and if-branch in the already-initted case - that + a write barrier in the init case - all wrapped into a single int. which is slightly, but not much better than a mutex. It is also slightly better than most implementations of boost::once/pthread_once, and much better than some, depending on platform. -------------- What I've found that pthread_once implementations end up using DBCL anyway but the benefit of using it there is obviously that you don't have to debug it since they put in the necessary barriers. As far as I'm concerned the problem is solved. For the 0.0001% of C++ programmers that actually need the performance and are willing to shell out the debugging hours, they are more than welcome. I (personally) think a boost singleton based on boost once would be good enough for everyone else until there are solutions per os/hw combination. Do you think people would like one? Not to take away from your valid points of course. Sohail

1 0

Re: [Boost-users] [general question] on threading and double checkedlocking pattern
by Sohail Somani 22 Jan '07

22 Jan '07

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Ovanes Markarian > > I might be wrong here, but I would like to hear some thoughts > of C++ professionals. > > I read in lots of sources about DCLP and how it is broken in > conjunction with Singleton pattern > and my question is of a very simple nature. Is it possible to > solve this problem by introducing > function calls via function pointers? Or is there still a > way, that these calls might be inlined > and if yes then how could this look like? This example is not > about freeing the singleton, it is > just about creating it. Hi, Perhaps the path-of-least-debugging is to use boost::once? Sohail

2 1

[general question] on threading and double checked locking pattern
by Ovanes Markarian 22 Jan '07

22 Jan '07

I might be wrong here, but I would like to hear some thoughts of C++ professionals. I read in lots of sources about DCLP and how it is broken in conjunction with Singleton pattern and my question is of a very simple nature. Is it possible to solve this problem by introducing function calls via function pointers? Or is there still a way, that these calls might be inlined and if yes then how could this look like? This example is not about freeing the singleton, it is just about creating it. class Singleton; typedef Singleton* (*singleton_getter)(); class Singleton : boost::noncopyable { static Singleton* pInstance; static singleton_getter getter; //other internal data... Singleton(); static Singleton* creating_singleton_getter(); static Singleton* non_creating_singleton_getter(); public: static Singleton* instance(); }; //implementation Singleton* Singleton::pInstance = NULL; singleton_getter Singleton::getter = &creating_singleton_getter; Singleton::Singleton() {} Singleton* Singleton::creating_singleton_getter() { //aquire mutex here if(Singleton::pInstance==NULL) Singleton::pInstance = new Singleton; Singleton::getter = &non_creating_singleton_getter; return Singleton::pInstance; } //mutex unlocked Singleton* Singleton::non_creating_singleton_getter() { //no mutex anymore return Singleton::pInstance; } Singleton* Singleton::instance() { return (Singleton::getter)(); } With Kind Regards, Ovanes Markarian

2 1

[date_time] Misparses POSIX timezone specs
by Stephen Turner 22 Jan '07

22 Jan '07

If I'm being stupid, tell me; but I believe the date_time library misreads all POSIX timezone specs by swapping + and -. It uses negative for west of Greenwich, but POSIX (admittedly unintuitively) uses negative for east of Greenwich. Compare this Linux box: [chiark:~] (1)% date Fri Jan 19 16:05:53 GMT 2007 [chiark:~] (2)% setenv TZ PST8 [chiark:~] (3)% date Fri Jan 19 08:06:04 PST 2007 with this code which wraps the date_time library (the internals aren't important): DWORD dw1 = 1149163201; // 1 June 2006 12:00:01 GMT CMyTime::set_timezone_posix("PST8"); CMyTime t = dw1; h = t.GetHour(); // h = 20 -- Stephen Turner, Cambridge, UK http://homepage.ntlworld.com/adelie/stephen/ "The internet is a reflection of our society. If we do not like what we see, the problem is not to fix the mirror, we have to fix society." (Vint Cerf)

2 1

[bind] Problem compiling when passing instantiation of class
by Paul Giaccone 22 Jan '07

22 Jan '07

I am using Boost bind in conjunction with Boost unit test, as I have many times before, but I can't get my code to compile. I've looked at http://boost.org/libs/bind/bind.html#Troubleshooting but don't see anything that covers my case. Here is the line that is failing (with disguised variable names): test_suite -> add(BOOST_TEST_CASE(boost::bind(my_test, obj1, obj2, obj3, 1.0, obj4, 10, 1E-9, results))); and here is the error that Microsoft Visual C++ .NET is generating: main.cpp(152): error C2665: 'boost::bind' : none of the 2 overloads can convert parameter 4 from type 'Obj3Type' The variables obj3 and obj4 are of type Obj3Type and Obj4Type respectively (see definitions below): The function my_test is defined as: void my_test(boost::shared_array<Vector>& a, boost::shared_array<Vector>& b, Obj3Type& c, const double d, const Obj4Type& e, const unsigned int f, const double g, boost::shared_array<std::pair<double, std::valarray<double> > >& h) where Obj3Type and Obj4Type are defined as: class Obj3Type { bool var1; unsigned int var2; unsigned int var3; double var4; double var5; MyType var6; boost::scoped_array<int> var7; boost::scoped_array<boost::scoped_array<double> > var8; }; struct Obj4Type { MyType var1; double var2; double var3; double var4; double var5; double var6; Vector var7; Vector var8; double var9; bool var10; } where MyType is an enumerated type and Vector is another struct of mine. (Where I have used structs rather than classes, this is for convenience.) Note that obj4 does not generate a compiler error, even when I move it to appear before obj3 in the parameter list. I wondered if it was necessary to overload operator= for Obj3Type as, presumably, the compiler cannot generate it for the scoped arrays in that struct but can for everything in Obj4Type, including Vector, for which I have defined operator=. I wrote an operator= for Obj3Type, but it made no difference to the compiler error. This was to be expected really, as obj3 is passed by reference rather than by value. Does it have anything to do with using structs instead of classes? I can't see how that could be the case. So what am I missing here? Thanks for any help.

2 2

Glib::ustring and tokenizer
by Manuel Jung 22 Jan '07

22 Jan '07

Hi everybody, I want to use Glib::ustring for UTF8 support. I was using boost::tokenizer up to this moment for breaking up some strings, which now would be ustrings. In the tokenizer Documentation you can find: template < class TokenizerFunc = char_delimiters_separator<char>, class Iterator = std::string::const_iterator, class Type = std::string > class tokenizer Im never used template programming, so can somebody give me a hint, if and how i can modify this to Glib::ustring? Maybe something like this? template < class TokenizerFunc = char_delimiters_separator<char>, class Iterator = Glib::ustring::const_iterator, class Type = Glib::ustring > class utokenizer Can i use wchar_t now? im a liddle bit confused, if it not works i have just to write some code myself, but i have hope getting it working. Thanks for reading and maybe some answers. Greetings from stormy germany Manuel Jung

3 4

Re: [Boost-users] [filesystem] code pages support
by Nat Goodspeed 22 Jan '07

22 Jan '07

________________________________________ From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of ????? ???????? Sent: Friday, January 19, 2007 10:41 AM To: boost-users(a)lists.boost.org Subject: [Boost-users] [filesystem] code pages support namespace fs = boost :: filesystem; boost :: intmax_t filesize = fs :: file_size (argv [1]); This causes an exception if the name consists of cyrillic symbols. (Windows XP, MinGW). Does boost :: filesystem support these names. [Nat] Maybe try: boost :: intmax_t filesize = fs :: file_size (fs::path(argv [1], fs::no_check)); This uses an explicit conversion to fs::path rather than an implicit one, which allows you to explicitly disable the path syntax checker. I always disable the path syntax checker. It doesn't even support ASCII names well. ;-)

1 0

Newby question re (boost::shared_ptr) enable_shared_from_this
by ethann.castell＠caliton.com 22 Jan '07

22 Jan '07

Hi, I'm still fairly new to C++ and I'm in the process of converting pointers to boost shared pointers. I have a question regarding the use of enable_shared_from_this. I would like to store a self-referencing pointer within the object. Something like: class someclass : public boost::enable_shared_from_this<someclass> { protected: boost::shared_ptr<someclass> m_ptr_this; someclass() { m_ptr_this = shared_from_this(); } } And then access m_ptr_this in classes derived from someclass, and pass as a parameter to methods of other (derived or non-derived) classes. eg. class someclass2 : public someclass { ... some_func(){ someclass3* f = new someclass3(); someclass3->do_something( m_ptr_this ); } } I understand that using a shared_ptr (without enable_shared_from_this) to self-reference will lead to problems because the reference count of the pointer will never reach zero and therefore the memory will never get released. But as enable_shared_from_this uses a weak pointer internally, does this get around the problem? I'm getting a little confused because it gets typecast from weak_ptr to shared_ptr and I'm not sure what this leads to. I've also considered having a member function return the pointer: boost::shared_ptr<someclass> someclass::get_this() { return shared_from_this(); } and then calling the routine like this; someclass3->do_something( get_this() ); but I think that this will cause a problem because the documentation says not to use boost pointers which are only created as temporary variables. i.e. store all boost pointers in vars. What I'm hoping to do is avoid having to declare extra shared_ptr vars all over the place. Any help will be most appreciated. And I'll owe you a beer! Regards Ethann Castell

3 5

program_options: Why it throw ambiguous_option?
by Peng Yu 22 Jan '07

22 Jan '07

Hi, I got the following error for the program list below. Where program_options considers "help" and "help_abc" as ambiguous? $ ./main --help terminate called after throwing an instance of 'boost::program_options::ambiguous_option' what(): ambiguous option help Aborted Thanks, Peng #include <boost/program_options.hpp> namespace po = boost::program_options; int main(int ac, char* av[]) { po::options_description desc("Allowed options"); desc.add_options() ("help", "produce help message") ("help_abc", po::value<int>(), "set compression level") ; po::variables_map vm; po::store(po::parse_command_line(ac, av, desc), vm); po::notify(vm); return 0; }

1 0

[Fusion] General comments
by Sohail Somani 22 Jan '07

22 Jan '07

Hi, FWIW. I think Fusion is a really good library. Having the results of algorithms be lazily evaluated was genius. Now I need to just find more excuses to use it :) One minor doc suggestion: A full TOC not unlike the MPL TOC would be very helpful for looking up stuff. One has to click through maybe 3 levels before finding out they went to the wrong place (Ok, doesn't happen that often anymore.. but still) Is it possible to get quickbook(?) to do that? Thanks, Sohail

2 1

[fusion] accumulate documentation
by Chris Weed 22 Jan '07

22 Jan '07

Hi, I've tried some code similar to the example here: <http://spirit.sourceforge.net/dl_more/fusion_v2/libs/fusion/doc/html/fusion…> but to get it to compile I have to make the inner function class 'result' instead of 'apply'. Chris

2 1

Does boost::thread_group::create_thread have memory leak?
by pete＠mu.org 22 Jan '07

22 Jan '07

I've been trying to track down memory leak being reported by valgrind. There are others out there who appear to have the same problem, but I can't find any reference to it in the boost list archives. I know valgrind can be inaccurate, but it seems pretty accurate every where else in my program. I've narrowed it down to something like this: ----------------- #include <boost/bind.hpp> #include <boost/thread.hpp> #include <iostream> void fn(){ return; } int main() { boost::thread_group thrd; thrd.create_thread(boost::bind(&fn)); thrd.join_all(); return 0; } ----------------- Valgrind is showing this: ... by 0x4053D76: boost::thread_group::create_thread(boost::function0<void, std::allocator<boost::function_base> > const&) (in /usr/lib/libboost_thread-mt.so.1.33.1) LEAK SUMMARY: ==22004== definitely lost: 0 bytes in 0 blocks. ==22004== possibly lost: 144 bytes in 1 blocks. ==22004== still reachable: 0 bytes in 0 blocks. ==22004== suppressed: 0 bytes in 0 blocks. Any clues? Thoughts? Thanks, Pete

5 15

Boost.Filesystem in C++/CLI?
by George Faraj 22 Jan '07

22 Jan '07

Has anyone tried to use Boost.Filesystem with C++/CLI? I'm trying to get some code that worked correctly in my native application to work on my C++/CLI program. The code is in a header file in a native C++ static library. inline void execute_files(std::string const& dir, std::string const& match, bool recursive = true, lua_State* interpreter = 0) { namespace bfs = boost::filesystem; bfs::path dirpath(dir); // (1) if (!bfs::exists(dirpath)) return; if (!interpreter) interpreter = lua_interpreter(); bfs::directory_iterator end_itr; for (bfs::directory_iterator itr(dirpath); itr != end_itr; ++itr) { if (!bfs::is_directory(*itr)) { if (itr->leaf().find(match) != std::string::npos) execute_file(itr->string()); } else if (recursive) { execute_files(itr->string(), match, recursive, interpreter); } } } The problem I'm having happens in the constructor of bfs::path (namely line (1)) at the first recursive call. An exception is thrown which I can't seem to get a helpful message from. It seems the string returned from itr->string() is invalid. Has anyone tried to use Boost.Filesystem in C++/CLI before? Any ideas on what could be causing this problem? Thanks, George Faraj

1 0

[Boost.Serialization] compilation error with xlc compiler
by DAN LEIBOVICH 21 Jan '07

21 Jan '07

Hi, I am trying to work with the serialization lib (1.33.1) on aix 5.3 with xlc compiler. I tried to compile the demp.cpp and got the error below. Is there any workaround ? Thanks in advance, Dan "../boost/boost_1_33_1/boost/archive/detail/oserializer.hpp", line 333.13: 1540-1109 (S) The use of undefined class "boost::STATIC_ASSERTION_FAILURE<0>" is not valid. "../boost/boost_1_33_1/boost/archive/detail/oserializer.hpp", line 331.50: 1540-0700 (I) The previous message was produced while processing "boost::archive::detail::save_pointer_type<boost::archive::text_oarchive,bus_stop *>::abstract<bus_stop>::register_type(boost::archive::text_oarchive &)". "../boost/boost_1_33_1/boost/archive/detail/oserializer.hpp", line 360.16: 1540-0700 (I) The previous message was produced while processing "boost::archive::detail::save_pointer_type<boost::archive::text_oarchive,bus_stop *>::register_type<bus_stop>(boost::archive::text_oarchive &, bus_stop &)". "../boost/boost_1_33_1/boost/archive/detail/oserializer.hpp", line 460.55: 1540-0700 (I) The previous message was produced while processing "boost::archive::detail::save_pointer_type<boost::archive::text_oarchive,bus_stop *>::invoke(boost::archive::text_oarchive &, bus_stop * const)". "../boost/boost_1_33_1/boost/archive/detail/oserializer.hpp", line 536.5: 1540-0700 (I) The previous message was produced while processing "boost::archive::save<boost::archive::text_oarchive,bus_stop *>(text_oarchive &, bus_stop * const &)". "../boost/boost_1_33_1/boost/archive/basic_text_oarchive.hpp", line 78.9: 1540-0700 (I) The previous message was produced while processing "boost::archive::basic_text_oarchive<boost::archive::text_oarchive>::save_override<bus_stop * const>(bus_stop * const &, int)". "../boost/boost_1_33_1/boost/archive/detail/interface_oarchive.hpp", line 77.15: 1540-0700 (I) The previous message was produced while processing "boost::archive::detail::interface_oarchive<boost::archive::text_oarchive>::operator<< <bus_stop * const>(bus_stop * const &)". "../boost/boost_1_33_1/boost/serialization/nvp.hpp", line 72.10: 1540-0700 (I) The previous message was produced while processing "boost::serialization::nvp<bus_stop * const>::save<boost::archive::text_oarchive>(text_oarchive &, const unsigned int) const". "../boost/boost_1_33_1/boost/serialization/access.hpp", line 87.17: 1540-0700 (I) The previous message was produced while processing "boost::serialization::access::member_save<boost::archive::text_oarchive,const boost::serialization::nvp<bus_stop * const> >(text_oarchive &, const nvp<bus_stop * const> &, const unsigned int)". "../boost/boost_1_33_1/boost/serialization/split_member.hpp", line 43.13: 1540-0700 (I) The previous message was produced while processing "boost::serialization::detail::member_saver<boost::archive::text_oarchive,boost::serialization::nvp<bus_stop * const> >::invoke(boost::archive::text_oarchive &, const boost::serialization::nvp<bus_stop * const> &, const unsigned int)". "../boost/boost_1_33_1/boost/serialization/split_member.hpp", line 61.13: 1540-0700 (I) The previous message was produced while processing "boost::serialization::split_member<boost::archive::text_oarchive,boost::serialization::nvp<bus_stop * const> >(text_oarchive &, nvp<bus_stop * const> &, const unsigned int)". "../boost/boost_1_33_1/boost/serialization/nvp.hpp", line 87.5: 1540-0700 (I) The previous message was produced while processing "boost::serialization::nvp<bus_stop * const>::serialize<boost::archive::text_oarchive>(text_oarchive &, const unsigned int)". "../boost/boost_1_33_1/boost/serialization/access.hpp", line 104.17: 1540-0700 (I) The previous message was produced while processing "boost::serialization::access::serialize<boost::archive::text_oarchive,boost::serialization::nvp<bus_stop * const> >(text_oarchive &, nvp<bus_stop * const> &, const unsigned int)". "../boost/boost_1_33_1/boost/serialization/serialization.hpp", line 81.5: 1540-0700 (I) The previous message was produced while processing "boost::serialization::serialize<boost::archive::text_oarchive,boost::serialization::nvp<bus_stop * const> >(text_oarchive &, nvp<bus_stop * const> &, const unsigned int)". "../boost/boost_1_33_1/boost/serialization/serialization.hpp", line 140.9: 1540-0700 (I) The previous message was produced while processing "boost::serialization::serialize_adl<boost::archive::text_oarchive,boost::serialization::nvp<bus_stop * const> >(text_oarchive &, nvp<bus_stop * const> &, const unsigned int)". "../boost/boost_1_33_1/boost/archive/detail/oserializer.hpp", line 253.13: 1540-0700 (I) The previous message was produced while processing "boost::archive::detail::save_non_pointer_type<boost::archive::text_oarchive,boost::serialization::nvp<bus_stop * const> >::save_only::invoke(boost::archive::text_oarchive &, const boost::serialization::nvp<bus_stop * const> &)". "../boost/boost_1_33_1/boost/archive/detail/oserializer.hpp", line 322.9: 1540-0700 (I) The previous message was produced while processing "boost::archive::detail::save_non_pointer_type<boost::archive::text_oarchive,boost::serialization::nvp<bus_stop * const> >::invoke(boost::archive::text_oarchive &, const boost::serialization::nvp<bus_stop * const> &)". "../boost/boost_1_33_1/boost/archive/detail/oserializer.hpp", line 536.5: 1540-0700 (I) The previous message was produced while processing "boost::archive::save<boost::archive::text_oarchive,boost::serialization::nvp<bus_stop * const> >(text_oarchive &, const nvp<bus_stop * const> &)". "../boost/boost_1_33_1/boost/archive/basic_text_oarchive.hpp", line 78.9: 1540-0700 (I) The previous message was produced while processing "boost::archive::basic_text_oarchive<boost::archive::text_oarchive>::save_override<const boost::serialization::nvp<bus_stop * const> >(const nvp<bus_stop * const> &, int)". "../boost/boost_1_33_1/boost/archive/detail/interface_oarchive.hpp", line 77.15: 1540-0700 (I) The previous message was produced while processing "boost::archive::detail::interface_oarchive<boost::archive::text_oarchive>::operator<< <const boost::serialization::nvp<bus_stop * const> >(const nvp<bus_stop * const> &)". "../boost/boost_1_33_1/boost/serialization/collections_save_imp.hpp", line 43.12: 1540-0700 (I) The previous message was produced while processing "boost::serialization::stl::save_collection<boost::archive::text_oarchive,std::list<bus_stop *,std::allocator<bus_stop *> > >(text_oarchive &, const list<bus_stop *,std::allocator<bus_stop *> > &)". "../boost/boost_1_33_1/boost/serialization/list.hpp", line 44.5: 1540-0700 (I) The previous message was produced while processing "boost::serialization::save<boost::archive::text_oarchive,bus_stop *,std::allocator<bus_stop *> >(text_oarchive &, const list<bus_stop *,std::allocator<bus_stop *> > &, const unsigned int)". "../boost/boost_1_33_1/boost/serialization/split_free.hpp", line 37.17: 1540-0700 (I) The previous message was produced while processing "boost::serialization::free_saver<boost::archive::text_oarchive,std::list<bus_stop *,std::allocator<bus_stop *> > >::invoke(boost::archive::text_oarchive &, const std::list<bus_stop *,std::allocator<bus_stop *> > &, const unsigned int)". "../boost/boost_1_33_1/boost/serialization/split_free.hpp", line 74.5: 1540-0700 (I) The previous message was produced while processing "boost::serialization::split_free<boost::archive::text_oarchive,std::list<bus_stop *,std::allocator<bus_stop *> > >(text_oarchive &, list<bus_stop *,std::allocator<bus_stop *> > &, const unsigned int)". "../boost/boost_1_33_1/boost/serialization/list.hpp", line 75.5: 1540-0700 (I) The previous message was produced while processing "boost::serialization::serialize<boost::archive::text_oarchive,bus_stop *,std::allocator<bus_stop *> >(text_oarchive &, list<bus_stop *,std::allocator<bus_stop *> > &, const unsigned int)". "../boost/boost_1_33_1/boost/serialization/serialization.hpp", line 125.13: 1540-0700 (I) The previous message was produced while processing "boost::serialization::serialize_adl<boost::archive::text_oarchive,std::list<bus_stop *,std::allocator<bus_stop *> > >(text_oarchive &, list<bus_stop *,std::allocator<bus_stop *> > &, const unsigned int)". "../boost/boost_1_33_1/boost/archive/detail/oserializer.hpp", line 148.5: 1540-0700 (I) The previous message was produced while processing "boost::archive::detail::oserializer<boost::archive::text_oarchive,std::list<bus_stop *,std::allocator<bus_stop *> > >::save_object_data(basic_oarchive &, const void *) const". "../boost/boost_1_33_1/boost/archive/detail/oserializer.hpp", line 99.7: 1540-0700 (I) The previous message was produced while processing "class boost::archive::detail::oserializer<boost::archive::text_oarchive,std::list<bus_stop *,std::allocator<bus_stop *> > >". "../boost/boost_1_33_1/boost/serialization/access.hpp", line 109.10: 1540-0217 (S) "serialize" is not a member of "class list<bus_stop *,std::allocator<bus_stop *> >". "../boost/boost_1_33_1/boost/serialization/access.hpp", line 104.17: 1540-0700 (I) The previous message was produced while processing "boost::serialization::access::serialize<boost::archive::text_oarchive,std::list<bus_stop *,std::allocator<bus_stop *> > >(text_oarchive &, list<bus_stop *,std::allocator<bus_stop *> > &, const unsigned int)". "../boost/boost_1_33_1/boost/serialization/serialization.hpp", line 81.5: 1540-0700 (I) The previous message was produced while processing "boost::serialization::serialize<boost::archive::text_oarchive,std::list<bus_stop *,std::allocator<bus_stop *> > >(text_oarchive &, list<bus_stop *,std::allocator<bus_stop *> > &, const unsigned int)". --------------------------------- Cheap Talk? Check out Yahoo! Messenger's low PC-to-Phone call rates.

2 3

Receiving a segfault from the variables_map destructor
by Stephen Torri 21 Jan '07

21 Jan '07

In the user interface program I created for a personal library I used the boost program options to provide two command line options to the user. The first is to report a help menu and the second is input used with the library's API. What I am getting is that there is a segfault in destructor for the variable map. Here is the backtrace: #0 0xb7469099 in __gnu_cxx::__exchange_and_add () from /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/libstdc++.so.6 #1 0xb744e039 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string () from /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/libstdc++.so.6 #2 0x0804d7c2 in ~pair (this=0x8054dc8) at /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/bits/stl_pair.h:69 #3 0x0804d801 in __gnu_cxx::new_allocator<std::pair<std::string const, boost::program_options::variable_value> >::destroy (this=0xbfa75d93, __p=0x8054dc8) at /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/ext/new_allocator.h:109 #4 0x0804e1ad in std::_Rb_tree<std::string, std::pair<std::string const, boost::program_options::variable_value>, std::_Select1st<std::pair<std::string const, boost::program_options::variable_value> >, std::less<std::string>, std::allocator<std::pair<std::string const, boost::program_options::variable_value> > >::destroy_node (this=0xbfa75e98, __p=0x8054db8) at /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/bits/stl_tree.h:391 #5 0x0804e232 in std::_Rb_tree<std::string, std::pair<std::string const, boost::program_options::variable_value>, std::_Select1st<std::pair<std::string const, boost::program_options::variable_value> >, std::less<std::string>, std::allocator<std::pair<std::string const, boost::program_options::variable_value> > >::_M_erase (this=0xbfa75e98, __x=0x8054db8) at /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/bits/stl_tree.h:1266 #6 0x0804e261 in ~_Rb_tree (this=0xbfa75e98) at /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/bits/stl_tree.h:578 #7 0x0804e2b1 in ~map (this=0xbfa75e98) at /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/bits/stl_map.h:93 #8 0x0804e31a in ~variables_map (this=0xbfa75e90) at /usr/include/boost/program_options/variables_map.hpp:110 #9 0x0804bec6 in main (ac=2, av=0xbfa75ff4) at pe_reverse.cpp:48 My system information is: gcc-4.1.1-r3 (Gentoo x86) boost-1.33.1-r1 (compiled with debug flag on and no symbols stripped) My user interface program is below. Now you will notice that I am not using the value retrieve from the "file" command line option. What I noticed was that regardless what value "file" contained it was the presence of the --file command line option which triggered the segmentation fault. So I just hardwired my program so that I could check to see if I could track down the segfault. #include <Reverse.h> #include <iostream> #include <Parsing_Exception.hpp> #include <boost/program_options.hpp> int main ( int ac, char** av ) { // Declare the supported options. boost::program_options::options_description desc("Allowed options"); desc.add_options() ("help", "produce help message") ("file", boost::program_options::value<std::string>(), "file to reverse"); boost::program_options::variables_map vm; boost::program_options::store(boost::program_options::parse_command_line(ac, av, desc), vm); boost::program_options::notify(vm); if (vm.count("help")) { std::cout << desc << std::endl; return 1; } if (vm.count("file")) { std::cout << "File to analyze was set to " << vm["file"].as<std::string>() << "." << std::endl; } /* else { std::cout << "File to analyze was not set." << std::endl; return 0; } */ try { libreverse::api::Reverse r_obj; r_obj.execute ( "kernel32.dll", //vm["file"].as<std::string>(), libreverse::api::Input_Types::BINARY, libreverse::api::Output_Types::CPLUSPLUS ); } catch ( errors::Parsing_Exception& pe ) { std::cerr << "Exception: " << pe.name() << std::endl; std::cerr << pe.what() << std::endl; } return 0; } I cannot see what is wrong. Now GCC had a minor revision update lately from 4.1.1-r2. Perhaps what I am running into is a non-boost library which is called by the program options and giving back a bad value. Stephen

1 0