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

[boost::concept_check] Question about possible feature
by Ovanes Markarian 02 Nov '06

02 Nov '06

Hi! Thanks for the great library. Currently I have to deal with constants as template parameters and I wonder, why there is no library to model constant concepts. Like: template<class T, size_t MAX_SIZE> struct Allocator { Allocator()throw(); }; template<class T, size_t MAX_SIZE> Allocator<T,MAX_SIZE>::Allocator()throw() { boost::function_requires<ConstGreaterThen<MAX_SIZE,O> >(); } I understand I could model it with BOOST_MPL_ASSERT etc. But would not it be better to unite all these features in one lib? With Kind Regards, Ovanes Markarian

2 2

microsec_clock not recognized in VC8
by Cheng, Victor S 01 Nov '06

01 Nov '06

> I'm using 1.33.1 date_time library, but ran into a problem with > microsec_clock. It's not recognized in VC8: > > error C2653: 'microsec_clock' : is not a class or namespace name > > If I change it to second_clock, then it's fine. Is this a known > problem for VC8? > ---- Here is my test code -------- #include "boost/date_time/posix_time/posix_time.hpp" #include <iostream> int main() { using namespace boost::posix_time; using namespace boost::gregorian; ptime now = microsec_clock::local_time(); //second_clock::local_time(); ... } ----- Here is how I built the library ---- "C:\Program Files\Microsoft Visual Studio 8"\vc\bin\vcvars32.bat c: cd \dev\boost_1_33_1 bjam -sTOOLS=vc-8_0 --prefix=C:\Dev\Boost --without-python --builddir=build install ------------------------------------------------------------------------------ This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice. -------- IRS Circular 230 Disclosure: Please be advised that any discussion of U.S. tax matters contained within this communication (including any attachments) is not intended or written to be used and cannot be used for the purpose of (i) avoiding U.S. tax related penalties or (ii) promoting, marketing or recommending to another party any transaction or matter addressed herein.

2 1

Re: [Boost-users] [boost.serialization] serialization crash
by RIVASSEAU Jean Noel 01 Nov '06

01 Nov '06

I've had the same problems. The problem is with the bool field. Code restoring the archive crashes if the bool stored in the archive is not equal to 0 or 1. But since you did not write a constructor in the Obj class, the boolean will actually be initialized with anything( eg, read 14675002 for example), and will be serialized that way in the archive since it seems the serialization code does not check if the bool is equal to 0 or 1 (only the restoration code). So, the solution is to initialize your boolean correctly and be very careful whenever you use booleans. However, I think the Serialization code should be fixed (remove the check for 0 or 1, it probably does more bad than good. Jean-Noël ________________________________ De : boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] De la part de Pavlo Korzhyk Envoyé : jeudi 26 octobre 2006 16:09 À : boost-users(a)lists.boost.org Objet : [Boost-users] [boost.serialization] serialization crash The following code crashes under cygwin+boost1.33 and under mingw+boost1.33 I create text archive in a file, and then serialization crashes when restoring object from that archive. The problem seem to be with bool field, if I replace bool x; with int x; in the class Obj implementation, everything runs fine. Is this a bug in serialization code? #include <iostream> #include <sstream> #include <fstream> #include <vector> #include <map> using namespace std; #include <boost/archive/text_oarchive.hpp> #include <boost/archive/text_iarchive.hpp> #include <boost/serialization/vector.hpp> #include <boost/serialization/map.hpp> using namespace boost; using namespace boost::serialization; class Obj { friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & x; } public: bool x; }; class Item; class Cheq : public Obj{ friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & boost::serialization::base_object<Obj>(*this); ar & v; ar & id; } public: vector<Item> v; int id; Cheq(){} }; class Item{ friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & a; ar & s; } public: int a; string s; }; class Row{ friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & m1; ar & m2; } public: map<string,string> m1,m2; }; class Data{ friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & a; ar & m; ar & cheque; } public: int a; map<string,string> m; map<int,Cheq> cheque; }; BOOST_CLASS_TRACKING(Data, boost::serialization::track_never) #include "boost/serialization/export.hpp" BOOST_CLASS_EXPORT(Data); BOOST_CLASS_EXPORT(Cheq); BOOST_CLASS_EXPORT(Item); int main(int argc, char** argv) { Data d; d.cheque[0]=Cheq(); //if(argc>1 && argv[1][0]=='1') { ofstream os("datfile"); boost::archive::text_oarchive oar(os); oar << d; } //if(argc>1 && argv[1][0]=='2') { ifstream is("datfile"); boost::archive::text_iarchive iar(is); iar >> d; } cout << "without crash\n"; return 0; } -- WBR, Pavlo Korzhyk ICQ#155870780

4 5

boost filesystem
by Aubrey, Jason 01 Nov '06

01 Nov '06

Hi, When I run the following program it runs successfully but throws an exception during shutdown. I don't know why, but it seems that the call to boost::filesystem::file_size() is corrupting memory somehow. This example only shows the call to file_size() but I think I've seen similar trouble with other calls within boost::filesystem. Am I doing something wrong here or is this a bug? Regards, Jason Aubrey ---------------------- Environment: OS: Win2k Compiler: VS7.1 Boost: v1.33.1 ---------------------- #include <boost/filesystem/operations.hpp> #include <fstream> int main(int, char**) { // Create a file using namespace std; const string fileName("/temp/test.txt"); ofstream file; file.open(fileName.c_str()); const string message("this is a test"); file << message; file.close(); const boost::intmax_t fileSize = boost::filesystem::file_size(fileName); if( fileSize != message.size() ) throw std::exception("Bad result"); return 0; } ---------------------- The following pop-up occurs during program completion: Window Title="Microsoft Visual C++ Debug Library" Window Icon=Critical Error Window Text=" Debug Assertion Failed! Program: .... File: dbgdel.cpp Line: 52 Expression: _BLOCK_TYPE_IS_VALID(pHead->nBlockUse) For information on how your program can cause an assertion failure, see the Visual C++ documentation on asserts. (Press Retry to debug the application)" Buttons=[Abort] [Retry] [Ignore]

3 4

boost/format/alt_sstream_impl.hpp fails on Solaris
by Martin Lester 31 Oct '06

31 Oct '06

boost/format/alt_sstream_impl.hpp fails to compile on Solaris with Sun Studio 11 compiler (I think). The error complains about being unable to assign a void* to a char* on line 248. I believe an explicit cast fixes this. Martin. (Apologies for diff filenames.) ---- --- alt_sstream_impl.hpp?revision=1.9 2006-10-31 22:55:23.000000000 +0000 +++ alt_sstream_impl.hpp 2006-10-31 22:55:58.000000000 +0000 @@ -245,7 +245,7 @@ add_size /= 2; if(0 < add_size) { new_size += add_size; - newptr = alloc_.allocate(new_size, is_allocated_? oldptr : 0); + newptr = (Ch *) alloc_.allocate(new_size, is_allocated_? oldptr : 0); } if(0 < prev_size) ___________________________________________________________ Copy addresses and emails from any email account to Yahoo! Mail - quick, easy and free. http://uk.docs.yahoo.com/trueswitch2.html

1 0

Re: [Boost-users] boost filesystem
by Lawrence Spector 31 Oct '06

31 Oct '06

I'm running on WinXP with VS7.1 and Boost v1.33.1. I compiled and tried it and was able to reproduce the error. Whenever you open a file, you should always do a check on file.fail() to make sure it opened successfully. You didn't, so you didn't realize the error happened earlier. Boost correctly threw an exception when you tried to check the size of the file. #include <boost/filesystem/operations.hpp> #include <fstream> #include <iostream> int main() { try { // Create a file using namespace std; const string fileName("/temp/test.txt"); ofstream file; file.open(fileName.c_str()); if (file.fail()) { throw std::runtime_error("Unknown file"); } const string message("this is a test"); file << message; file.close(); const boost::intmax_t fileSize = boost::filesystem::file_size(fileName); if( fileSize != message.size() ) throw std::exception("Bad result"); } catch(std::exception& e) { std::cout << "Caught fatal error: " << e.what() << std::endl; } catch(...) { std::cout << "Caught unknown error" << std::endl; } std::cin.get(); // so the window stays up to view output return 0; } Output: Caught fatal error: Unknown file. You probably wanted to make your path C:\temp\test.txt, since it's a Windows program, right? -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Rush Manbert Sent: Tuesday, October 31, 2006 2:45 PM To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] boost filesystem Aubrey, Jason wrote: > > Replies are at the end of this message: > Aubrey, Jason wrote: > >>Hi, >> >>When I run the following program it runs successfully but throws an >>exception during shutdown. I don't know why, but it seems that the >>call to boost::filesystem::file_size() is corrupting memory somehow. >>This example only shows the call to file_size() but I think I've seen >>similar trouble with other calls within boost::filesystem. >> >>Am I doing something wrong here or is this a bug? >> >>Regards, >>Jason Aubrey >> >>---------------------- >> >>Environment: >> OS: Win2k >> Compiler: VS7.1 >> Boost: v1.33.1 >> >>---------------------- >> >>#include <boost/filesystem/operations.hpp> #include <fstream> >> >>int main(int, char**) >>{ >> // Create a file >> using namespace std; >> const string fileName("/temp/test.txt"); >> ofstream file; >> file.open(fileName.c_str()); >> const string message("this is a test"); >> file << message; >> file.close(); >> >> const boost::intmax_t fileSize = >>boost::filesystem::file_size(fileName); >> >> if( fileSize != message.size() ) >> throw std::exception("Bad result"); >> >> return 0; >>} >> > > > Either I'm missing something, or... > > file_size takes a path reference as its calling argument. You're passing > a string. How does this even compile? > > - Rush > _______________________________________________ > > Thanks for the Reply Rush. > > If I modify the above code to contain the following I still see the same > behavior: > const boost::filesystem::path filePath(fileName); > const boost::intmax_t fileSize = > boost::filesystem::file_size(filePath); > > Regards, > Jason Aubrey > _______________________________________________ > > Would you be able to print out what the values of message.size() and > fileSize are, right before you do that comparison? > > Thanks, > Lawrence Spector > _______________________________________________ > > Both fileSize and message.size() are 14. The exception thrown is not a > result of the if-block, but the result of a check by the runtime when it > does its cleanup during program shutdown. > Hi Jason, Well, it's too bad that the Easy Answer wasn't the correct answer. :-) I made a console app using VS2005 and Boost 1.33.1, and used your exact code as my main routine. It just works. I also tried setting things up so that my debug build would link against the release version of the library, because the last person that was having filesystem problems had done that, but it just works in that case too. So I'm afraid that I can't reproduce your problem with my Windows setup. If you run your app under the debugger and break when it gets the error, can you tell what sort of object it's trying to delete by backtracking up the stack? That might give some hint about what's happening. Best regards, Rush _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

3 2

Portable SafeInt?
by Troels Arvin 31 Oct '06

31 Oct '06

Hello, I'm wondering: Does Boost have a class like Microsoft's SafeInt? (Portable, of course.) If not: Does anyone have some good guidelines on how to make code (on Linux) integer overflow safe? (Here: Safe == exception generating.) I'm thinking specialized compilers, etc. -- Regards, Troels Arvin <troels(a)arvin.dk> http://troels.arvin.dk/

2 2

Re: [Boost-users] boost filesystem
by Lawrence Spector 31 Oct '06

31 Oct '06

Hmm that's even more interesting, maybe a 2k vs. XP compability issue? The file fails when trying to open on my system. I don't have a 2k system to try it on, so I don't know how much more assistance I can be. Based on the posts so far in this thread, though, I get the impression that different users are getting different results, which is definitely concerning. If I get a chance, I'll try it on my Fedora system tonight and see what happens. In the meantime, good luck. -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Aubrey, Jason Sent: Tuesday, October 31, 2006 4:43 PM To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] boost filesystem Thanks for your suggestion Lawrence but I don't think it's related to the problem. I added the following after opening the file but it doesn't throw (since the file is valid): if( !file.is_open() ) throw std::exception("Unable to open file"); To prove that the file is valid: 1) I verified that the program creates the file 2) main() completes as expected. The following is in regard to Rush's comment: The call stack when trouble occurs is as follows: msvcr71d.dll!operator delete(void * pUserData=0x00343418) msvcp71d.dll!std::allocator<char>::deallocate(char * _Ptr=0x00343418, unsigned int __formal=48) msvcp71d.dll!std::string::_Tidy(bool _Built=true, unsigned int _Newsize=0) msvcp71d.dll!std::string::~string() TestsD.exe!$E2() msvcr71d.dll!doexit(int code=0, int quick=0, int retcaller=0) msvcr71d.dll!exit(int code=0) TestsD.exe!mainCRTStartup() kernel32.dll!7c816d4f() ntdll.dll!7c915b4f() kernel32.dll!7c8399f3() The offending code within delete() is: _ASSERTE(_BLOCK_TYPE_IS_VALID(pHead->nBlockUse)); Unfortunately, I couldn't make any sense of the data in or near the bad block. Regards, Jason ---------------------- Environment: OS: Win2k Compiler: VS7.1 Boost: v1.33.1 ---------------------- #include <boost/filesystem/operations.hpp> #include <fstream> // Contrary to simplicity I've enhanced the following to satisfy suggestions int main(int, char**) { // Create a file using namespace std; const string fileName("/temp/test.txt"); ofstream file; file.open(fileName.c_str()); if( !file.is_open() ) throw std::exception("Unable to open file"); const string message("this is a test"); file << message; file.close(); const boost::filesystem::path filePath(fileName); const boost::intmax_t fileSize = boost::filesystem::file_size(filePath); if( fileSize != message.size() ) throw std::exception("Bad result"); return 0; // This line is reached without trouble } _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

Re: [Boost-users] boost filesystem
by Lawrence Spector 31 Oct '06

31 Oct '06

Would you be able to print out what the values of message.size() and fileSize are, right before you do that comparison? Thanks. -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Aubrey, Jason Sent: Tuesday, October 31, 2006 1:12 PM To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] boost filesystem Replies are at the end of this message: Aubrey, Jason wrote: > Hi, > > When I run the following program it runs successfully but throws an > exception during shutdown. I don't know why, but it seems that the > call to boost::filesystem::file_size() is corrupting memory somehow. > This example only shows the call to file_size() but I think I've seen > similar trouble with other calls within boost::filesystem. > > Am I doing something wrong here or is this a bug? > > Regards, > Jason Aubrey > > ---------------------- > > Environment: > OS: Win2k > Compiler: VS7.1 > Boost: v1.33.1 > > ---------------------- > > #include <boost/filesystem/operations.hpp> #include <fstream> > > int main(int, char**) > { > // Create a file > using namespace std; > const string fileName("/temp/test.txt"); > ofstream file; > file.open(fileName.c_str()); > const string message("this is a test"); > file << message; > file.close(); > > const boost::intmax_t fileSize = > boost::filesystem::file_size(fileName); > > if( fileSize != message.size() ) > throw std::exception("Bad result"); > > return 0; > } > Either I'm missing something, or... file_size takes a path reference as its calling argument. You're passing a string. How does this even compile? - Rush _______________________________________________ Thanks for the Reply Rush. If I modify the above code to contain the following I still see the same behavior: const boost::filesystem::path filePath(fileName); const boost::intmax_t fileSize = boost::filesystem::file_size(filePath); Regards, Jason Aubrey _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

3 2

Serialization problem on 64-bit Windows release
by Sigurd Saue 31 Oct '06

31 Oct '06

We've started to use boost serialization and I've run into problems with serialization of derived classes. The "funny" thing is that this happens only on 64-bit Windows release compiled with MS Visual 2005. The same code works fine on Linux 32/64 bit debug/release, on Windows 32-bit debug/release and on Windows 64-bit debug. But not Windows 64-bit release. We use boost version 1.33.1. Here's the code that causes problems (Parameter is the base class, ParamCollection is a vector of Parameters): template<class Archive> static void serialize(Archive & ar, ParamCollection & col, const unsigned int /*version*/) { ar.register_type(static_cast<FloatParameter*>(NULL)); ar.register_type(static_cast<IntParameter*>(NULL)); ar.register_type(static_cast<ChoiceParameter*>(NULL)); ar.register_type(static_cast<StringParameter*>(NULL)); ar.register_type(static_cast<BlobParameter*>(NULL)); ar & boost::serialization::base_object<std::vector<Parameter*> >(col); } When serializing the ParamCollection (serializing, not deserializing) an archive exception is thrown: unregistered class. I've tried to use both abstract and non-abstract base class without any success. I did some research in the boost code and found that the exception was thrown in polymorphic::save (oserializer.hpp) by the last condition (NULL == bpos_ptr). Any clues? Is there a workaround? Thanks, Sigurd

3 4