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

Memory leak with STL containers and pool_allocator?
by Georgios Diamantopoulos 11 Jan '06

11 Jan '06

Hello everyone, I am experiencing a memory leak while using pool_allocator with std::vector. I am detecting this with _CrtDumpMemoryLeaks() on MSVC8. The full program listing is at the end of the program. The leaks reported are: Detected memory leaks! Dumping objects -> {122} normal block at 0x00356518, 520 bytes long. Data: < e5 e5 $e5 (e5 > 1C 65 35 00 20 65 35 00 24 65 35 00 28 65 35 00 {121} normal block at 0x003563D0, 264 bytes long. Data: < c5 c5 c5 c5 > D4 63 35 00 D8 63 35 00 DC 63 35 00 E0 63 35 00 {120} normal block at 0x00356308, 136 bytes long. Data: < c5 c5 c5 c5 > 0C 63 35 00 10 63 35 00 14 63 35 00 18 63 35 00 Object dump complete. This could be due to a static object being destroyed after main() returns but I couldn't know that without knowing the implementation of pool_allocator. I have tried getting mem checkpoints at the beginning and end of main and detecting the leaks that way which I *think* would get around static objects but without any difference. Thanks, Georgios #define CRTDBG_MAP_ALLOC #include <cstdlib> #include <crtdbg.h> #include <stdexcept> #if defined(_DEBUG) inline void* __cdecl operator new(size_t nSize) { void* pResult = _malloc_dbg(nSize, _NORMAL_BLOCK, NULL, 0); if (pResult != NULL) return pResult; else throw std::bad_alloc(); return pResult; } inline void __cdecl operator delete(void* p) { _free_dbg(p, _NORMAL_BLOCK); } inline void* __cdecl operator new[](size_t nSize) { return ::operator new(nSize); } inline void __cdecl operator delete[](void* p) { ::operator delete(p); } inline void* __cdecl operator new(size_t nSize, int nType, const char * lpszFileName, int nLine) { void* pResult = _malloc_dbg(nSize, nType, lpszFileName, nLine); if (pResult != NULL) return pResult; else throw std::bad_alloc(); return pResult; } inline void* __cdecl operator new[](size_t nSize, int nType, const char * lpszFileName, int nLine) { return ::operator new(nSize, nType, lpszFileName, nLine); } inline void* __cdecl operator new(size_t nSize, const char * lpszFileName, int nLine) { return ::operator new(nSize, _NORMAL_BLOCK, lpszFileName, nLine); } inline void* __cdecl operator new[](size_t nSize, const char * lpszFileName, int nLine) { return ::operator new[](nSize, _NORMAL_BLOCK, lpszFileName, nLine); } inline void __cdecl operator delete(void* pData, const char * /* lpszFileName */, int /* nLine */) { ::operator delete(pData); } inline void __cdecl operator delete[](void* pData, const char * /* lpszFileName */, int /* nLine */) { ::operator delete(pData); } #define DEBUG_NEW new(THIS_FILE, __LINE__) #endif // _DEBUG #include <vector> #include <boost/pool/pool_alloc.hpp> #ifdef _DEBUG #define new DEBUG_NEW #undef THIS_FILE static char THIS_FILE[] = __FILE__; #endif int main(void) { std::vector<int, boost::pool_allocator<int> > data_points; for(int i = 0; i < 100; ++i) { data_points.push_back(i); } data_points.~vector(); boost::singleton_pool<boost::pool_allocator_tag, sizeof(int)>::release_memory(); _CrtDumpMemoryLeaks(); return 0; }

1 0

How to use Boost.Array library
by yinglcs2＠yahoo.com 11 Jan '06

11 Jan '06

In Java, I can create an array based on the value of an input parameter of a function: int[] func (int size) { int[] rtn = new int[size]; // do something return rtn; } Can you please tell me if I can do the same with the Boost.Array library? >From the example I see, I can only declare the size of the array during declaration (not dynamically, the rhs in my example). If I can't do that with Boost.Array, is there any other solution? Thank you. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

Getting Started documentation: minor update request
by Lonnie Princehouse 11 Jan '06

11 Jan '06

Hello, I'm trying to get boost-build up and running on Linux so that I can build the Python bindings for Boost.Graph, and after a few hours of fiddling around I'm thoroughly confused and frustrated. Please, could someone who understands boost-build could tell me what I'm doing wrong? (Note: I added the boost-build.jam file, which points to the installation directory of boost-build, and the project-root.jam which is just two newlines, copied from the "hello" example.) -------------------------------------------------------------------------------------------------- bash$ ls Jamfile LICENSE_1_0.txt boost build project-root.jam src Jamrules README boost-build.jam example python test bash$ bjam /usr/local/share/boost-build/build/project-roots.jam:368: in project-root warning: rulename $(project-root).$(method) expands to empty string Jamfile:13: in modules.load /usr/local/share/boost-build/build/project.jam:255: in load-jamfile /usr/local/share/boost-build/build/project.jam:67: in project.load /usr/local/share/boost-build/build-system.jam:75: in load /usr/local/share/boost-build/kernel/modules.jam:259: in import /usr/local/share/boost-build/kernel/bootstrap.jam:120: in boost-build /home/princelj/boost_graph/bgl-python-0.9/boost-build.jam:1: in module scope Jamfile:19: in modules.load rule subinclude unknown in module Jamfile</home/princelj/boost_graph/bgl-python-0.9>. /usr/local/share/boost-build/build/project.jam:255: in load-jamfile /usr/local/share/boost-build/build/project.jam:67: in project.load /usr/local/share/boost-build/build-system.jam:75: in load /usr/local/share/boost-build/kernel/modules.jam:259: in import /usr/local/share/boost-build/kernel/bootstrap.jam:120: in boost-build /home/princelj/boost_graph/bgl-python-0.9/boost-build.jam:1: in module scope ---------------------------------------------------------------------------------- The Jamfile that came with bgl-python looks like this: # Copyright 2005 The Trustees of Indiana University. # Use, modification and distribution is subject to the Boost Software # License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at # http://www.boost.org/LICENSE_1_0.txt) # Authors: Douglas Gregor # Andrew Lumsdaine # This file builds the Python bindings for the Boost Graph Library and # the Parallel BGL. project-root ; # Only build release-mode binaries, unless the user explicitly # requests otherwise BUILD ?= release ; subinclude build ; subinclude build/distributed ; ------------------------------------------------------------------------------ Boost, bjam, and boost-build (V2) are the latest (non-CVS) releases from boost.org, installed as per the "Getting Started" instructions on boost.org. I have no idea what's going wrong. I read on the list archive that "subinclude" only exists in perforce-jam, not bjam, so I emerged perforce jam and tried it with no more success: $ jam warning: unknown rule project-root warning: unknown rule subinclude warning: unknown rule subinclude ...found 7 target(s)... Please help! (This is using Gentoo Linux, although boost/bjam/boost-build were installed from scratch and not using the ebuilds)

2 2

Re: [Boost-users] Boost Math Library
by Sliwa, Przemyslaw (London) 11 Jan '06

11 Jan '06

Please have a look at GSL. It is a C lib but can be used with C++. Kind regards Pshemek Przemyslaw Sliwa Global Foreign Exchange FX Risk Engine Development Merrill Lynch ( +44 (0)20 7995 4182 ) +44 (0)79 6325 2319 * Email: przemyslaw_sliwa(a)ml.com -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of yinglcs2(a)yahoo.com Sent: 10 January 2006 07:29 To: boost-users(a)lists.boost.org Subject: [Boost-users] Boost Math Library Hi, Does Boost Math Library support Statistic Calculation? (e.g. median, std deviation, etc)? >From here, it does not appear Boost Math library calculate has statistic algorithm. If not, can someone please recommend some c/c++ library which does statistics? Thank you. http://www.boost.org/libs/libraries.htm#Algorithms Math and numerics * math - Several contributions in the domain of mathematics, from various authors. * numeric/conversion - Optimized Policy-based Numeric Conversions, from Fernando Cacciola. * integer - Headers to ease dealing with integral types. * interval - Extends the usual arithmetic functions to mathematical intervals, from Guillaume Melquiond, Hervé Brönnimann and Sylvain Pion. * math/common_factor - Greatest common divisor and least common multiple, from Daryle Walker. * math/octonion - Octonions, from Hubert Holin. * math/quaternion - Quaternions, from Hubert Holin. * math/special_functions - Mathematical special functions such as atanh, sinc, and sinhc, from Hubert Holin. * multi_array - Multidimensional containers and adaptors for arrays of contiguous data, from Ron Garcia. * operators - Templates ease arithmetic classes and iterators, from Dave Abrahams and Jeremy Siek. * random - A complete system for random number generation, from Jens Maurer. * rational - A rational number class, from Paul Moore. * uBLAS - Basic linear algebra for dense, packed and sparse matrices, from Joerg Walter and Mathias Koch. __________________________________________ Yahoo! DSL - Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users -------------------------------------------------------- If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ --------------------------------------------------------

2 1

[serialization] [wave] [spirit] Can't compile boost cvs
by Peter Whaite 10 Jan '06

10 Jan '06

Since before Christmas I haven't been able to compile the cvs serialization xml files. It looks like something in spirit. Wave also fails to compile with the same errors. I'm a bit surprised I haven't seen this mentioned on the boost lists, though I see there are many failures in the boost regression notifications. % gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5) % bjam --with-serialization 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). ...found 4780 targets... ...updating 48 targets... gcc-C++-action bin/boost/libs/serialization/build/libboost_serialization.a/gcc/debug/xml_grammar.o In file included from /misc/hdb1/local-src/boost_cvs/boost/spirit/core/scanner/skipper.hpp:16, from /misc/hdb1/local-src/boost_cvs/boost/spirit/core/composite/impl/directives.ipp:16, from /misc/hdb1/local-src/boost_cvs/boost/spirit/core/primitives/primitives.hpp:16, from /misc/hdb1/local-src/boost_cvs/boost/spirit/utility/chset.hpp:15, from /misc/hdb1/local-src/boost_cvs/boost/archive/impl/basic_xml_grammar.hpp:69, from /misc/hdb1/local-src/boost_cvs/libs/serialization/src/xml_grammar.cpp:16: /misc/hdb1/local-src/boost_cvs/boost/spirit/core/primitives/impl/primitives.ipp:190: new declaration `template<class CharT> boost::enable_if<boost::spirit::impl::use_char_traits<CharT>, std::char_traits<_CharT>::int_type>::type boost::spirit::impl::to_int_type(CharT)' /misc/hdb1/local-src/boost_cvs/boost/spirit/core/primitives/impl/primitives.ipp:171: ambiguates old declaration `template<class CharT> boost::disable_if<boost::spirit::impl::use_char_traits<CharT>, CharT>::type boost::spirit::impl::to_int_type(CharT)' /misc/hdb1/local-src/boost_cvs/boost/spirit/core/primitives/impl/primitives.ipp:199: new declaration `template<class CharT> boost::enable_if<boost::spirit::impl::use_char_traits<CharT>, CharT>::type boost::spirit::impl::to_char_type(CharT)' /misc/hdb1/local-src/boost_cvs/boost/spirit/core/primitives/impl/primitives.ipp:179: ambiguates old declaration `template<class CharT> boost::disable_if<boost::spirit::impl::use_char_traits<CharT>, CharT>::type boost::spirit::impl::to_char_type(CharT)' set -e "g++" -c -DBOOST_LIB_DIAGNOSTIC=1 -g -O0 -fno-inline -Wall -ftemplate-depth-255 -Wno-non-virtual-dtor -Wno-ctor-dtor-privacy -I"bin/boost/libs/serial ization/build" -I "/misc/hdb1/local-src/boost_cvs" -o "bin/boost/libs/serialization/build/libboost_serialization.a/gcc/debug/xml_grammar.o" "/misc/hdb1/lo cal-src/boost_cvs/libs/serialization/build/../src/xml_grammar.cpp" "/usr/bin/objcopy" --set-section-flags .debug_str=contents,debug "bin/boost/libs/serialization/build/libboost_serialization.a/gcc/debug/xml_grammar.o" ...failed gcc-C++-action bin/boost/libs/serialization/build/libboost_serialization.a/gcc/debug/xml_grammar.o... gcc-C++-action bin/boost/libs/serialization/build/libboost_serialization.a/gcc/debug/xml_iarchive.o ...interrupted ...failed updating 1 target... -- Peter Whaite (http://whaite.ca)

2 1

[serialization] : Documentation
by nitin motgi 10 Jan '06

10 Jan '06

Hi, I think a sentence has to be modified in the documentation. On the link http://www.boost.org/libs/serialization/doc/index.html Section : Pending Issues [ Added >> << ] currently can't serialize through a pointer an object >>a of<< class that implements its own new/delete operators. I was wondering whether it is "object a". to currently can't serialize through a pointer an object >>of a<< class that implements its own new/delete operators. Thank you, -- Nitin Motgi NITIN . DOT. MOTGI .AT. GMAIL .DOT. COM

1 0

Re: [Boost-users] [BULK] Re: [Test] Running a specific Test Suite
by Sohail Somani 10 Jan '06

10 Jan '06

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Gennadiy Rozental > Sent: Tuesday, January 10, 2006 11:03 AM > To: boost-users(a)lists.boost.org > Subject: [BULK] Re: [Boost-users] [Test] Running a specific Test Suite > Importance: Low > > > > Is there a flag I can pass to the test program or any other > way to run > > only a specific Test Suite, ignoring the other ones? > > Hopefully by the end of this release cycle I will add an > ability to run tests by name, which should satisfy this request. I am not yet a user of boost unit test, but is there a way of listing all the tests/targets as well? That could be very useful. I still wish this was a feature in scons!

2 1

iterators 2
by jens-theisen＠gmx.de 10 Jan '06

10 Jan '06

Hello, Thanks for the references, I briefly looked at them (Views and any_iterator) and wasn't aware of them beforehand. I'm not really looking for a solution to a particular problem I might have, but rather wondering if there is not something very basic missing from C++. In many other programming languages there is a good notion for talking about a collection of things conveniently. Python and the .NET languages have this with their iterator concepts. C++ only has it's iterators currently, which is not always a very good solution for reasons alread said. Especially, for the starting problem of my original posting, there is no natural solution. True, there is any_iterator: We can define the virtual function in my original problem as typedef boost::iterator_range< adobe::any_iterator< ... > > ret_range; class X : ... { virtual ret_range give_stuff() const; ... It's still a monstrosity, however, given that any_iterator has 4 template parameters, is derived from iterator_facade, and the iterator_range doubles this even. Presumably, a library author would quickly write his own little nonstandard iterator interface himself and have the virtual function return this instead. It would be nice to have something lightweight enough to promote its use a bit like boost::shared_ptr has become "the obvious way" of dealing with dynamic objects in C++. What I like to have is something more lightweight, along the following requirements: - the "notion" of a collection of things as a concrete type rather than a concept - fast to compile, simple error messages, fun to use, it should be the obvious choice for a library programmer to give collections of things (rather than awkward input iterators derived from iterator_facade) - a toolbox of free functions to combine them in all the ways I can do with linked lists in functional languages - performance and memory usage don't have to be optimal if we're just talking about the cost of a virtualisation A while ago, I made a first attempt on this, making the following design decisions: - There is no concept, but just one templated type: class list< typename reference >; which has various implementations and is, despite the name, conceptually a forward traversal iterator which is aware of the end of its range. - lists are constructed by using a number of free functions only, notably - the make_list overload set, implementing construction from stuff like iterators, containers, etc. and - map, filter, concat, etc. for combining lists in useful ways. - lists have conversion operators along the line of the conversion of their underlying reference type, which especially enables list< T const& > to be used where list< T > is expected. - lists are not iterators, but they can export that behaviour. If this feature isn't used, iterator_facade don't have to be present. (If viewed as iterators, their end is a default constructed list, as usual.) The most important thing that's lacking, however, is that lists are conceptually forward traversal only. Actually, I'm not entirely convinced that it would really be necessary to have more than that (or less). My impression is that virtualisation for more than forward traversal is less dearly needed. I can only think of somewhat contrived examples. What do you think? If other forms of traversal are important, this would complexify all of this quite a bit. Presumably there would be a class hierarchy reflecting the traversal concepts, and possibly each such hiearchy for the implementations as well. But what should free function like map return then? There would have to be overloads for each of the traversal types, and there are already other reasons for overloads. How do people think on this matter? What direction to go? Is this worth spending time on? Cheers, Jens

2 2

[Test] Running a specific Test Suite
by Edson Tadeu 10 Jan '06

10 Jan '06

Is there a flag I can pass to the test program or any other way to run only a specific Test Suite, ignoring the other ones? Thanks in advance

2 1

Boost Serialization: extended_type_info_no_rtti not working...
by RIVASSEAU Jean Noel 10 Jan '06

10 Jan '06

Hello, I am trying to learn the Boost Serialization Library. Although I like the fundamental principles of the library, using the library so far has proven a nightmare for my project. To be more precise: I need to serialize objects via pointers to base class. And I need to do it without RTTI. While using extended_type_info_no_rtti for my classes I always get an "unregistered_class" exception at run time. But I have done the following: in all my classes, in the implementation unit (.cpp) I have included explicitely the headers needed for the archives I use: #include <boost/archive/text_oarchive.hpp> #include <boost/archive/text_iarchive.hpp> Then I have something like that in each class: #include <boost/serialization/base_object.hpp> #include <boost/serialization/type_info_implementation.hpp> #include <boost/serialization/extended_type_info_no_rtti.hpp> #include <boost/serialization/export.hpp> namespace boost { namespace serialization { template<class Archive> void serialize(Archive & ar, PrimitiveMemberVariableSpecification & m, const unsigned int version) { ar & boost::serialization::base_object<MemberVariableSpecification>(m); ar & m.unused_primitive_type; } } // namespace serialization } // namespace boost BOOST_CLASS_TYPE_INFO( PrimitiveMemberVariableSpecification, extended_type_info_no_rtti<PrimitiveMemberVariableSpecification> ) BOOST_CLASS_EXPORT(PrimitiveMemberVariableSpecification) (Here the name of the class is PrimitiveMemberVariableSpecification. I also want to report a bug in the documentation: the doc says that you should write: BOOST_CLASS_TYPE_INFO( ClassName, extended_type_info_no_rtti<BaseClassName> ) Although the example test_no_rtti.cpp uses the following syntax: BOOST_CLASS_TYPE_INFO( ClassName, extended_type_info_no_rtti<ClassName> ) I think that the example is right, not the documentation. ) Normally the BOOST_CLASS_EXPORT should *register* all my classes. Why doesn't it work? I have of course also written a correct get_key() virtual function for all my classes. If I just change extended_type_info_no_rtti to extended_type_info_typeid, everything works fine, but I do want extended_type_info_no_rtti. Also, keeping everything in the headers files seems to be a nightmare, although that is what Robert Ramsey recommends. I get tons of multiple definitions errors at link time if I do that (something like: multiple definition of `boost::archive::detail::guid_initializer<MemberVariableSpecification>::instance' with gcc - MinGW 3.4.2) I have looked at the documentation for two days, read absolutely everything and still do not understand. Maybe I should look at the code ??? Thank you Jean-Noël

2 1