January 2009 - Boost-users - lists.boost.org

[thread] assertion error in timed_lock
by Ernst Murnleitner 11 Jan '09

11 Jan '09

Hello, Sometimes - especially if I start the program with valgrind - my program exits with /usr/include/boost/thread/pthread/recursive_mutex.hpp:180: bool boost::recursive_timed_mutex::timed_lock(const boost::system_time&): Assertion `!res || res==16' failed. The line 180 is in this function: bool timed_lock(system_time const & abs_time) { struct timespec const timeout=detail::get_timespec(abs_time); int const res=pthread_mutex_timedlock(&m,&timeout); BOOST_ASSERT(!res || res==EBUSY); return !res; } pthread_mutex_timedlock returned ETIMEDOUT. Can the BOOST_ASSERT be changed that it only logs a warning? In a production environment it is not nice, if the program exits. In the man page of pthread_mutex_timedlock I read: ----- ... The pthread_mutex_timedlock() function shall fail if: EINVAL The mutex was created with the protocol attribute having the value PTHREAD_PRIO_PROTECT and the calling thread's priority is higher than the mutex' current priority ceiling. EINVAL The process or thread would have blocked, and the abs_timeout parameter specified a nanoseconds field value less than zero or greater than or equal to 1000 million. ETIMEDOUT The mutex could not be locked before the specified timeout expired. ... ------ Isn't ETIMEDOUT a return value which has to be expected? Greetings, Ernst

2 1

[Spirit] Version question
by Peter Barker 11 Jan '09

11 Jan '09

Hello, I want to use Boost.Spirit to parse some data so I'm reading the documentation. I'm a little confused because the documentation linked to from 1.37.0 takes me to a Spirit user's guide apparently regarding "Spirit classic". Does Boost 1.37.0 include two Spirit versions? If so, do I need to be looking elsewhere for documentation on how to use the non-classic version? Essentially I want to use the latest version of Spirit that comes with Boost 1.37.0 and would like guidance on that please. Regards, Pete

2 3

[mp_math] Wrong sign for mp_int<> after addition.
by Jeroen N. Witmond 11 Jan '09

11 Jan '09

Greetings, I've stumbled across a problem in mp_math in the sandbox, revision 50541. The code below (a Boost.Test test case) demonstrates that the problem is present only for mp_int<> and not for int. The message I get is wrong-value.cpp(16): error in "Mixed_integers<N5boost7mp_math6mp_intISaIvENS0_13mp_int_traitsIjyEEEE>": check j == 4 failed [-4 != 4] Regards, Jeroen. #define BOOST_TEST_DYN_LINK #define BOOST_TEST_MODULE Wrong_sign #include <boost/test/unit_test.hpp> #include <boost/mp_math/mp_int.hpp> #include <boost/mpl/list.hpp> typedef boost::mpl::list< int, boost::mp_math::mp_int<> > test_types; BOOST_AUTO_TEST_CASE_TEMPLATE( Mixed_integers, Type, test_types ) { Type i(-1); BOOST_CHECK_EQUAL(i, -1); Type j = i + 5; BOOST_CHECK_EQUAL(j, 4); // Line 16. }

1 0

[GIL] trouble loading image files
by Kenny Riddile 11 Jan '09

11 Jan '09

This is my first time using GIL and I'm having some difficulty loading jpeg and png files. Here's some code: rgb8_image_t image1; jpeg_read_and_convert_image<rgb8_image_t>( "file.jpg", m_image1 ); rgb8_image_t image2; png_read_and_convert_image<rgb8_image_t>( "file.jpg", m_image2 ); Attempting to load the jpeg causes a crash at jpeg_read_header(&_cinfo,TRUE); in jpeg_io_private.hpp. Attempting to load the png causes a similar crash at png_read_info(_png_ptr, _info_ptr); in png_io_private.hpp. I'm using the libjpeg and libpng builds from these sites: http://gnuwin32.sourceforge.net/packages/jpeg.htm http://gnuwin32.sourceforge.net/packages/libpng.htm

1 1

[datetime] local_date_time and time zone issues
by Boris 10 Jan '09

10 Jan '09

I've been playing with local_date_time and time zones but don't understand the return values of utc_time(), local_time() and local_time_in(). Here's a small program: ---------- #include <boost/date_time/local_time/local_time.hpp> #include <iostream> int main() { boost::local_time::time_zone_ptr tz1(new boost::local_time::posix_time_zone("CET+1")); boost::posix_time::ptime pt1(boost::gregorian::date(2009, 1, 5), boost::posix_time::time_duration(12, 0, 0)); boost::local_time::local_date_time dt1(pt1, tz1); std::cout << dt1.utc_time() << std::endl; std::cout << dt1.local_time() << std::endl; boost::local_time::time_zone_ptr tz2(new boost::local_time::posix_time_zone("CET+2")); std::cout << dt1.local_time_in(tz2) << std::endl; } ---------- The output of this program is: 2009-Jan-05 12:00:00 2009-Jan-05 13:00:00 2009-Jan-05 14:00:00 CET The program uses CET which is the abbreviation for Central European Time which is UTC+1. If the UTC time is now 12:00:00 the local time in CET+1 must be 14:00:00 (and not 13:00:00). Accordingly the local time in CET+2 must be 15:00:00. Why Boost.DateTime appends "CET" to the local time in CET+2 I don't understand either. Is this a bug or do I misunderstand these functions? Boris

3 5

Boost Interprocess condition variables
by Federico Golfrè Andreasi 10 Jan '09

10 Jan '09

Hi! I'm using condition variables of Boost.interprocess 1.36.0 to manage a synchronized access to a shared memory segment by two tasks. I found a problem when: task 1 is waiting on a condition variable and task 2 crashes during his execution, so task 1 waits forever on that variable. How can I kill also task 1? thank you, Federico

3 4

[graph] Bundled properties in subgraphs
by Grzegorz Slodkowicz 10 Jan '09

10 Jan '09

Hello, It seems that bundled properties still don't work with subgraphs. I found a mention of the problem dating back to 2005 [1], a closed ticket for the issue [2] and another post [3], this time from 2008, with an ex tempore fix (which doesn't work for me). Could someone possibly account for that? [1] http://lists.boost.org/boost-users/2005/03/10844.php [2] https://svn.boost.org/trac/boost/ticket/380 [3] http://www.nabble.com/-graph--property_map-from-bundled-properties-in-a-sub… TIA, Greg Slodkowicz

2 3

[date_time] error with g++-4.3.2
by frederic.bron＠alcan.com 10 Jan '09

10 Jan '09

Using 1.37.0 on x86_64-pc-linux. I get the following error compiling a program that includes date_time.hpp with g++-4.3.2. The web site says that g++ 4.3.2 is tested for 1.37.0. Any clue? In file included from boost/date_time/local_time/tz_database.hpp:14, from boost/date_time/local_time/local_time.hpp:19, from boost/date_time.hpp:15, boost/date_time/tz_db_base.hpp:161: error: declaration of 'typedef class boost::date_time::dst_adjustment_offsets<typename time_zone_type::time_duration_type> boost::date_time::tz_db_base<time_zone_type, rule_type>::dst_adjustment_offsets' boost/date_time/time_zone_base.hpp:76: error: changes meaning of 'dst_adjustment_offsets' from 'class boost::date_time::dst_adjustment_offsets<typename time_zone_type::time_duration_type>' no particular error building boost; final message is only: ...updated 7627 targets... Frédéric Bron ___________________________________ Frédéric Bron (frederic.bron(a)alcan.com) Unité ALT, Alcan CRV, BP 27, 38341 Voreppe +33 4 76 57 81 72, +33 6 07 48 56 67 Avis : Ce message et toute pièce jointe sont la propriété d'Alcan et sont destinés seulement aux personnes ou à l'entité à qui le message est adressé. Si vous avez reçu ce message par erreur, veuillez le détruire et en aviser l'expéditeur par courriel. Si vous n'êtes pas le destinataire du message, vous n'êtes pas autorisé à utiliser, à copier ou à divulguer le contenu du message ou ses pièces jointes en tout ou en partie. Notice: This message and any attachments are the property of Alcan and are intended solely for the named recipients or entity to whom this message is addressed. If you have received this message in error please inform the sender via e-mail and destroy the message. If you are not the intended recipient you are not allowed to use, copy or disclose the contents or attachments in whole or in part.

3 4

BoostCon 2009: Submission deadline extended
by Hartmut Kaiser 10 Jan '09

10 Jan '09

Hi all, The deadline for the submission of session proposals has been extended to January 20th, 2009. No further extensions will be granted. Please find below the original call for participation. Conference registration will be available at http://www.boostcon.com/registration. Regards Hartmut ---------------------------------------------------------------------------- 3rd annual Boost Conference 2009 Aspen CO, USA, May 3-9, 2009, www.boostcon.com ---------------------------------------------------------------------------- Call for participation ---------------------- Promising to be the main face-to-face event for all things Boost (www.boost.org) BoostCon'09 opens the door to your C++ future. From using the Boost libraries to writing and maintaining them, from evangelizing to deploying Boost within your organization, from infrastructure and process to vision and mission, and from TR1 to TR2 and the new C++0x Standard, BoostCon brings together the sessions, the colleagues, and the inspiration to support your work with C++ and Boost in particular for the next year. To reflect the breadth of the Boost community, the conference includes sessions aimed at two constituencies: Boost end-users and hard-core Boost library and tool developers. The program fosters interaction and engagement within and across those two groups, with an emphasis on hands-on, participatory sessions. Session topics -------------- * Topics of interest include, but are not restricted to, the following: * General tutorial sessions introducing one or more Boost libraries * In-depth sessions on using specific libraries * Case studies on using Boost * Experts panels * Advanced sessions on implementation techniques used within Boost libraries * C++0x and how it will change life for users and library writers * TR1 and TR2 * Development workshops to extend or enhance existing Boost libraries * Workshops on design process * Infrastructure workshops such as Build tools, Website, Testing * Concepts and Generic Programming * Hardware and infrastructure presentations focused on how libraries can make better use of the technology * Other topics likely to be of great interest to Boost users and Developers. Interactive and collaborative sessions are encouraged, as this is the nature of both the on-line Boost community and the style of learning and participation that has proven most successful at such events. Sessions can be tutorial based, with an emphasis on interaction and participant involvement, or workshop based, whether hands-on programming or paper-based, discussion-driven collaborative work. Session formats --------------- Presentations ............. Presentations focus on a practitioner's ideas and experience with anything relevant to Boost and Boost users. Panels ...... Panels feature three or four people presenting their ideas and experiences relating to Boost's relevant, controversial, emerging, or unresolved issues. Panels may be conducted in several ways, such as comparative, analytic, or historic. Tutorials ......... Tutorials are sessions at which instructors teach conference participants specific Boost-relevant skills. Workshops ......... Workshops provide an active arena for advancements in Boost-relevant topics. Workshops provide the opportunity for experienced practitioners to develop new ideas about a topic of common interest and experience. Author's Corner Presentations ............................. These were introduced at BoostCon 2008, and were a great success. They are short (30 minute) sessions, focusing on tips on usage and design. In addition, we're looking to uncover the hidden design gems boost libraries. Tool Vendors Presentations .......................... We actively encourage tool vendors and ISP's to submit proposals for a special Tool Vendors Session Track aimed at products related to Boost and C++ (compilers, libraries, tools, etc.). Other formats may also be of interest. Don't hold back a proposal just because it doesn't fit into a pigeonhole. Submitting a proposal --------------------- Standard Sessions are 90 minutes. You may submit a proposal for fractions or multiples of 90-minutes. Fractional proposals will be grouped into 90 minute sessions covering related topics. Longer sessions, such as tutorials and classes, will be assigned 90 minute, three hour (i.e. half day), or six hour (i.e. full day) time slots. Please include: * The working title. * Type of session: presentation, panel, tutorial, workshop, authors corner, vendor track, other * A paragraph or two describing the topic covered, suitable for the conference web site * Proposed length: 10-20 minute short talks, 45 minutes, 90 minutes, half-day, full day * Alternate lengths, if you are willing to make adjustments: 10-20 minute lightning-talks, 45 minutes, 90 minutes, half-day, full day * Audience: users, developers, both * Level: basic, intermediate, advanced * A biography, suitable for the conference web site * Your contact information (will not be made public) Submission details ------------------ All submissions have to be done through the EasyChair conference management system: http://www.easychair.org/conferences/?conf=boostcon09. If you have not already registered at EasyChair, you will need to do so in order to submit your proposal. All submissions will go through a peer review process. Authors are invited to submit PDF versions of full papers of up to 10 pages in ACM conference proceedings format (see http://www.acm.org/sigs/publications/proceedings-templates) The full papers are not required unless you want them published in the proceedings. All accepted papers will be made available in the Association for Computing Machinery (ACM) Digital Library (approval pending). Best papers, after further reviews, will be considered to be book chapters or journal articles in a renowned journal. The session materials go on the BoostCon CD handed out to attendees. For general information on the BoostCon 2009 paper submission or the scope of technical papers solicited, please refer to the conference website at www.boostcon.com. For any other questions about the submission process or paper format, please contact the Program Committee at boostcon09(a)easychair.com. If you have any technical problems with EasyChair, please contact EasyChair for help. Note: Presenters must agree to grant a non-exclusive perpetual license to publish submitted materials, either electronically or in print, in any media related to BoostCon. Important dates --------------- Proposals for submissions due: January 20th 2009. Proposals acceptances sent (tentative program available): February 10th, 2009 Fully scheduled program available: March 1st, 2009 Session materials due: April 1st 2009. Hartmut Kaiser, email: hartmut.kaiser(a)gmail.com (Program Committee Chair) David Abrahams, email: dave(a)boostpro.com (Conference Chair) On behalf of the conference organizers

1 0

Re: [Boost-users] Boost-users Digest, Vol 1870, Issue 4
by niranjan bangera 10 Jan '09

10 Jan '09

i have done in the following way.. even am getting some errors, did i miss any of the headers, or added extra(added extra for sure). Any suggestions will be accepted #include <boost/serialization/utility.hpp> #include <boost/serialization/collection_traits.hpp> #include <boost/serialization/serialization.hpp> #include <boost/serialization/base_object.hpp> #include <fstream> #include <boost/archive/text_iarchive.hpp> #include <boost/archive/text_oarchive.hpp> #include <boost/serialization/assume_abstract.hpp> class fd; class base: class derived { ..... fd *ptr; ..... friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int file_version) { (void) file_version; ar & ptr; ar & boost::serialization::base_object<derived>(*this); } }; //end of class base Version::1.36.0 compliler: g++ 4.1.1.... i am getting a error : error: forward declaration of 'struct fd' /boost_1_36_0/include/boost-1_36/boost/serialization/access.hpp:109: error: inva lid use of undefined type 'struct /project/wipro_virtutech_nobackup/users/niranjan/project_new/boost_1_36_0/include/boost-1_36/boost/serialization/extended_type_info_typeid.hpp:117: note: neither the destructor nor the class-specific operator delete will be called, even if they are declared when the class is defined.

1 0