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

Re: [Boost-users] Trap in regex library (help requested)
by Marty Eaves 16 Jun '06

16 Jun '06

John, Thanks, I'll look into the STL compatibility. We were using STL port with VC6, but I think we are using the Microsoft STL with VC7. I'll double check. As far as test cases go, the regex string looks like this: "^(((((((((19)|(20)|(21)))){0,1}((((0)|(1)|(2)|(3)|(4)|(5)|(6)|(7)|(8)|( 9)))(((0)|(1)|(2)|(3)|(4)|(5)|(6)|(7)|(8)|(9))))){0,1}(((01)|(02)|(03)|( 04)|(05)|(06)|(07)|(08)|(09)|(10)|(11)|(12)))(((01)|(02)|(03)|(04)|(05)| (06)|(07)|(08)|(09)|(10)|(11)|(12)|(13)|(14)|(15)|(16)|(17)|(18)|(19)|(2 0)|(21)|(22)|(23)|(24)|(25)|(26)|(27)|(28)|(29)|(30)|(31)))))))" As back ground information, this string was generated from a SRGS date DTMF grammar. I am attempting to modify the code to try to determine which parts of the regex string where used in the match. This is necessary to implement support for the <tag> element in the SRGS grammar. I am looking into potentially trying to use "named groups" whenever a <tag> is encountered in the SRGS grammar as the "regex grammar" is getting generated. Thus I am starting to play with the extended match functionality. I have not modified any code yet, other than using the BOOST_REGEX_MATCH_EXTRA flag in user.hpp. This appears to cause the exception detailed in the call stack. The test case failing is using the above grammar with the value of into the "inputValue" parameter set to "2" in the code snippet below: else { // no termchar std::string tmpString; boost::match_results<std::string::const_iterator> what; try { boost::regex e(regex_grammar.c_str()); // return false for partial match, true for full match, or throw for // impossible match based on what we have so far... if(0 == boost::regex_match(inputData, what, e, boost::match_default | boost::match_partial | boost::match_extra)) { // the input so far could not possibly be valid so reject it: return SEQUENCE_NOMATCH; } } catch(...) { VXML_LOG::CLogBuff log(LOG_REC_SIZE,IVILOG_VXML_MODULE); log.WriteRecord("CDtmfGrammar_custom::check", // pTrm->GetLine(), 0, IVILOG_CLASS_TRACE, __FILE__,__LINE__, "Exception from Boost regex caught. Grammar = (%s)",regex_grammar.c_str()); return SEQUENCE_NOMATCH; } // OK so far so good, but have we finished? if(what[0].matched) { GRAMMAR_RETM_ITER iter=m_input_map.find(inputData.c_str()); if (iter != m_input_map.end()) { if(pResultValue) *pResultValue = (*iter).second; } else { if(pResultValue) { slotData = CDtmfGrammar::addWhiteSpaces(inputData); *pResultValue = slotData.c_str(); } } // excellent, we have a result: { boost::regex e(regex_grammar.c_str()); std::string newInput; bool matchOccurred = false; // loop thru 1 2 3 4 5 6 7 8 9 0 * # A B C D std::string charArray = "1234567890*#ABCD"; for(unsigned int x=0; x < charArray.length(); x++) { newInput = inputData + charArray.substr(x,1); if(0 != boost::regex_match(newInput, what, e, boost::match_default | boost::match_partial | boost::match_extra)) { matchOccurred = true; break; } } if(!matchOccurred) return SEQUENCE_OK; // we are done. } } // what we have so far is only a partial match... return SEQUENCE_MORE; } } ________________________________ Marty Eaves STAFF SOFTWARE ENGINEER CALL PROCESSING & MEDIA SERVICES RESEARCH AND DEVELOPMENT INTERVOICE, INC. P: (972) 454-8348 marty.eaves(a)intervoice.com ________________________________ Intervoice: Connecting People and Information. -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of John Maddock Sent: Thursday, June 15, 2006 1:22 PM To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] Trap in regex library (help requested) Marty Eaves wrote: > I am having an issue using the regex library. I am developing in VC7 > and this issue occurs with both Boost 1.33.0 and 1.33.1. I have > recently tried to start retrieving capture information in the regex > matches by using the match_result and sub_match classes. In order to > use these classes, the compile flag BOOST_REGEX_MATCH_EXTRA is > required > to be turned on (enabled in user.hpp). With the library is built with > this flag on, I will get the following trap when the method calling > regex_match() returns. Just a clarification: you only need that define if you want extended capture information. You can access regular Perl style marked sub-expressions perfectly well without it. > An unhandled exception of type 'System.NullReferenceException' > occurred > in tg12.exe > > > > Additional information: Object reference not set to an instance of an > object > > > > This exception appears to occur in the cleanup logic of the > ~match_results() destructor. I have yet to make any changes to the > code > to use the match_results object. In other words, the code I am using > worked previously without the BOOST_REGEX_MATCH_EXTRA flag enabled. > Are > there any compiler options required? No none, if I'm reading your stack trace right it's std::vector that's causing the failure: there's nothing fancy going on inside sub_match just a scoped_ptr to a vector or sub_matches. Do you have a test case I can look at? If you're using managed code (looks like you are?) you might want to double check to see if there are any known issues using that with the STL. John. _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users This e-mail transmission may contain information that is proprietary, privileged and/or confidential and is intended exclusively for the person(s) to whom it is addressed. Any use, copying, retention or disclosure by any person other than the intended recipient or the intended recipient's designees is strictly prohibited. If you are the intended recipient, you must treat the information in confidence and in accordance with all laws related to the privacy and confidentiality of such information. If you are not the intended recipient or their designee, please notify the sender immediately by return e-mail and delete all copies of this email, including all attachments.

2 1

[serialization] mac/windows difference
by Hugh Hoover 16 Jun '06

16 Jun '06

I have a test program (boost::test) for a set of my application classes. When run on darwin (10.4.6, gcc4.01) the tests work correctly - that is, I can serialize the structure to an XML archive and read it back (actually, all 3 archive types). When I run the same test on windows (XP sp2, vc8), the read back of the XML archive fails very early because it apparently can't find an appropriate class to instantiate. When I look at the XML output, the windows version has a class name at the point where it fails, while the darwin version does not (there are NO class names written in the darwin archive). The code between darwin and windows is essentially the same - there aren't any differences in MY code in the serialization code. Several points: a) The topmost level is a pointer (plain) to an abstract class - the concrete subclass being serialized is very simple at this point. b) The specific class that's failing is from an STL map with pointers to an abstract base class. 1) That particular failing class is successfully tested prior to where it fails in the same test application (output to all archive types and read-back). 2) although it's using a different archive to test, initialization of all archives is identical (register_type and register_void_pointer called as appropriate) c) There is one other class that also gets serialized with a class name in addition to it's ID (I presume this means that something's up with class registration?) Ok - any suggestions on how to tackle this? I can't find anything wrong in the registration (i've walked through my part of the registration code in the debugger). I'm using boost 1.33.1 Thanks Hugh Hoover Enumclaw Software

3 3

Re: [Boost-users] [serialization-1.32.0] de-serializing newer versions that the application can deal with
by Tarjei Knapstad 16 Jun '06

16 Jun '06

[sorry for breaking the threading, just re-joined the list] > We have system data written out to an XML archive and being > de-serialized at application startup. > > One object type in the archive we written at version 1 by a newer > version of the application. We then ran an older version of the > software which only understood version 0 of the object. Hi Russel, To handle different versions of data you should split serialize() into separate save()/load() functions as described in the tutorial: http://boost.org/libs/serialization/doc/tutorial.html#splitting The implementation will look something like: void save(...) { // Serialize all data here } void load(Archive & ar, unsigned int version) { if (version > 0) { // Load data added in version 1 } if (version > 1) { // Load data added in version 2 } // Load version 0 data } Regards, -- Tarjei

4 6

Boost.property_tree help
by Demetrius Cassidy 16 Jun '06

16 Jun '06

Reading the tutorial for property_tree, using the functions ptree.find, ptree.get and ptree.get_child, they will only return the topmost node, so if I had two different children nodes under my root named '<Logistics>' with different data within the children, I would only be able to access the first one. So my question is that how would I go about navigating to each top node under my root when they are all named the same? I basicly will have a file that looks something like this: XML file contents: <Technologies> <Logistics ID="Damage Diagnostics"> <DisplayName>Damage Diagnostics</DisplayName> <Cost>1500</Cost> <Description>Increases repair ability by 10%</Description> <RepairAbility>10</RepairAbility> <Requires>Advanced Starship Repair</Requires> <Category>Logistics</Category> <Model>lrgbuilding0</Model> <AIValue>30</AIValue> </Logistics> <Logistics ID="Basic Self-Repair"> /* I need to access this node */ <DisplayName>Basic Self-Repair</DisplayName> <Cost>3000</Cost> <Description>Increases repair ability by 10%</Description> <RepairAbility>10</RepairAbility> <Requires>Damage Diagnostics</Requires> <Category>Logistics</Category> <Model>controlgrav0</Model> <AIValue>40</AIValue> </Logistics> </Technologies> I will have a very large number of nodes with the same name under my root, but each will have different data in their children that I need to access. A full DOM parser is too much overhead when I do not need any validation, but rather I need to read a large number of configuration data across XML files. I really like the ease of use of this library, but I just can't figure this out. Any help would be greatly appreciated.

2 3

templatized constructor, destructor
by Gottlob Frege 16 Jun '06

16 Jun '06

Is there really no way to templatize a) a zero argument constructor b) a destructor ? I'm trying to delay the compile of the functions until everything is known... Tony

3 2

boost::regex: regex_constants::error_space
by Andriy Tylychko (mail.ru) 16 Jun '06

16 Jun '06

John Maddock wrote: * You shouldn't get that exception from that expression: that exception is raised when the number of states visted in the search for a match looks to be growing exponentially, it's usually caused by "pathological" regular expressions like "(.*)*" that can end up searching forever on some inputs. Do you have a more specific test case please? John. * Hi John. Thanks for quick reply. I'm afraid I don't have more specific test. Maybe additional info will help. Boost v.1.33.1, VC 8.0. The buffer content looks like: 00:00:00.000 [category 100] EXCEPTION: test log-message #100 00:00:00.000 [category 101] ERROR: test log-message #101 new line 00:00:00.000 [category 102] WARNING: test log-message #102 00:00:00.000 [category 103] INFO: test log-message #103 00:00:00.000 [category 104] DEBUG: test log-message #104 00:00:00.000 [category 105] EXCEPTION: test log-message #105 new line 00:00:00.000 [category 106] ERROR: test log-message #106 [...] 00:00:00.000 [category 300] EXCEPTION: test log-message #300 As result, threre's no match for "#1.*#7" in such content. Debugger shows that regex_search reached position "171\r\n00:00:00.000 [category 172] WARNING: test log-message #172[...]", state_count = 468663, max_state_count = 468640. Can I provide any additional useful info? Should I send you standalone test for problem reproduction? Thank you, Andriy. John Maddock wrote: > Andriy Tylychko (mail.ru) wrote: >> Hi, >> >> The code looks like: >> >> std::string buffer(10240, '\0'); >> // ... fill buffer >> boost::regex e("#1.*#7"); >> boost::smatch m; >> boost::regex_search(buffer, m, e); >> >> The buffer of 10KB is full of "something #x". As result I receive >> regex_constants::error_space at >> boost\regex\v4\perl_matcher_non_recursive.hpp:164. >> I'll highly appreciate any help. > > You shouldn't get that exception from that expression: that exception is > raised when the number of states visted in the search for a match looks to > be growing exponentially, it's usually caused by "pathological" regular > expressions like "(.*)*" that can end up searching forever on some inputs. > > Do you have a more specific test case please? > > John.

1 0

[Boost.Test]unit_test_example1.cpp and vc80
by obirsoy＠comcast.net 16 Jun '06

16 Jun '06

My problem is "access violation" in unit_test_example1.cpp can not be caught with vc80. Do I need to set some compiler or linker option? When I ran unit_test_example1 (compiled with vc71, boost version 1.32.0) I used to get this output. The access violation was reported and the test continued. >Running 1 test case... >c:/development/projects/test/boosttest/main.cpp(17): error in "free_test_function": check 2 == 1 failed >unknown location(0): fatal error in "free_test_function": memory access violation > >*** 1 failure detected (1 failure expected) in test suite "Unit test example 1" >Press any key to continue But with vc80 (both with 1.33.1 and cvs head), when I run unit_test_example1 I get the access violation dialog and after selecting "Don't Send" I get this output. Note I also get some memory leak dump if I ran it the debug version. >Running 1 test case... >./main.cpp(17): error in "free_test_function": check 2 == 1 failed >Press any key to continue . . . What am I missing? Thanks Orhun Birsoy

3 3

boost::regex: regex_constants::error_space
by Andriy Tylychko (mail.ru) 15 Jun '06

15 Jun '06

Hi, The code looks like: std::string buffer(10240, '\0'); // ... fill buffer boost::regex e("#1.*#7"); boost::smatch m; boost::regex_search(buffer, m, e); The buffer of 10KB is full of "something #x". As result I receive regex_constants::error_space at boost\regex\v4\perl_matcher_non_recursive.hpp:164. I'll highly appreciate any help. Thank you, Andriy Tylychko, telya(a)vichnavich.com

2 1

Trap in regex library (help requested)
by Marty Eaves 15 Jun '06

15 Jun '06

Hello, I am having an issue using the regex library. I am developing in VC7 and this issue occurs with both Boost 1.33.0 and 1.33.1. I have recently tried to start retrieving capture information in the regex matches by using the match_result and sub_match classes. In order to use these classes, the compile flag BOOST_REGEX_MATCH_EXTRA is required to be turned on (enabled in user.hpp). With the library is built with this flag on, I will get the following trap when the method calling regex_match() returns. An unhandled exception of type 'System.NullReferenceException' occurred in tg12.exe Additional information: Object reference not set to an instance of an object This exception appears to occur in the cleanup logic of the ~match_results() destructor. I have yet to make any changes to the code to use the match_results object. In other words, the code I am using worked previously without the BOOST_REGEX_MATCH_EXTRA flag enabled. Are there any compiler options required? The stack trace is below. Thanks, Marty > DtmfGrammarManager.dll!std::vector<boost::sub_match<std::basic_string<ch ar,std::char_traits<char>,std::allocator<char> >::const_iterator>,std::allocator<boost::sub_match<std::basic_string<cha r,std::char_traits<char>,std::allocator<char> >::const_iterator> > >::_Tidy() Line 797 + 0x3 C++ DtmfGrammarManager.dll!std::vector<boost::sub_match<std::basic_string<ch ar,std::char_traits<char>,std::allocator<char> >::const_iterator>,std::allocator<boost::sub_match<std::basic_string<cha r,std::char_traits<char>,std::allocator<char> >::const_iterator> > >::~vector<boost::sub_match<std::basic_string<char,std::char_traits<char >,std::allocator<char> >::const_iterator>,std::allocator<boost::sub_match<std::basic_string<cha r,std::char_traits<char>,std::allocator<char> >::const_iterator> > >() Line 389 C++ DtmfGrammarManager.dll!std::vector<boost::sub_match<std::basic_string<ch ar,std::char_traits<char>,std::allocator<char> >::const_iterator>,std::allocator<boost::sub_match<std::basic_string<cha r,std::char_traits<char>,std::allocator<char> >::const_iterator> > >::`scalar deleting destructor'() + 0xf C++ DtmfGrammarManager.dll!boost::checked_delete<std::vector<boost::sub_matc h<std::basic_string<char,std::char_traits<char>,std::allocator<char> >::const_iterator>,std::allocator<boost::sub_match<std::basic_string<cha r,std::char_traits<char>,std::allocator<char> >::const_iterator> > > >(std::vector<boost::sub_match<std::basic_string<char,std::char_traits<c har>,std::allocator<char> >::const_iterator>,std::allocator<boost::sub_match<std::basic_string<cha r,std::char_traits<char>,std::allocator<char> >::const_iterator> > > * x=0x00baadf0) Line 34 + 0x1c C++ DtmfGrammarManager.dll!boost::scoped_ptr<std::vector<boost::sub_match<st d::basic_string<char,std::char_traits<char>,std::allocator<char> >::const_iterator>,std::allocator<boost::sub_match<std::basic_string<cha r,std::char_traits<char>,std::allocator<char> >::const_iterator> > > >::~scoped_ptr<std::vector<boost::sub_match<std::basic_string<char,std:: char_traits<char>,std::allocator<char> >::const_iterator>,std::allocator<boost::sub_match<std::basic_string<cha r,std::char_traits<char>,std::allocator<char> >::const_iterator> > > >() Line 77 + 0xb C++ DtmfGrammarManager.dll!boost::sub_match<std::basic_string<char,std::char _traits<char>,std::allocator<char> >::const_iterator>::~sub_match<std::basic_string<char,std::char_traits<c har>,std::allocator<char> >::const_iterator>() + 0x12 C++ DtmfGrammarManager.dll!boost::sub_match<std::basic_string<char,std::char _traits<char>,std::allocator<char> >::const_iterator>::`scalar deleting destructor'() + 0xf C++ DtmfGrammarManager.dll!std::_Destroy<boost::sub_match<std::basic_string< char,std::char_traits<char>,std::allocator<char> >::const_iterator> >(boost::sub_match<std::basic_string<char,std::char_traits<char>,std::al locator<char> >::const_iterator> * _Ptr=0x008d8428) Line 50 C++ DtmfGrammarManager.dll!std::allocator<boost::sub_match<std::basic_string <char,std::char_traits<char>,std::allocator<char> >::const_iterator> >::destroy(boost::sub_match<std::basic_string<char,std::char_traits<char >,std::allocator<char> >::const_iterator> * _Ptr=0x008d8428) Line 152 + 0x9 C++ DtmfGrammarManager.dll!std::_Destroy_range<boost::sub_match<std::basic_s tring<char,std::char_traits<char>,std::allocator<char> >::const_iterator>,std::allocator<boost::sub_match<std::basic_string<cha r,std::char_traits<char>,std::allocator<char> >::const_iterator> > >(boost::sub_match<std::basic_string<char,std::char_traits<char>,std::al locator<char> >::const_iterator> * _First=0x008d8428, boost::sub_match<std::basic_string<char,std::char_traits<char>,std::allo cator<char> >::const_iterator> * _Last=0x008d8988, std::allocator<boost::sub_match<std::basic_string<char,std::char_traits< char>,std::allocator<char> >::const_iterator> > & _Al={...}, std::_Nonscalar_ptr_iterator_tag __formal={...}) Line 226 + 0xc C++ DtmfGrammarManager.dll!std::_Destroy_range<boost::sub_match<std::basic_s tring<char,std::char_traits<char>,std::allocator<char> >::const_iterator>,std::allocator<boost::sub_match<std::basic_string<cha r,std::char_traits<char>,std::allocator<char> >::const_iterator> > >(boost::sub_match<std::basic_string<char,std::char_traits<char>,std::al locator<char> >::const_iterator> * _First=0x008d8428, boost::sub_match<std::basic_string<char,std::char_traits<char>,std::allo cator<char> >::const_iterator> * _Last=0x008d8988, std::allocator<boost::sub_match<std::basic_string<char,std::char_traits< char>,std::allocator<char> >::const_iterator> > & _Al={...}) Line 217 + 0x28 C++ DtmfGrammarManager.dll!std::vector<boost::sub_match<std::basic_string<ch ar,std::char_traits<char>,std::allocator<char> >::const_iterator>,std::allocator<boost::sub_match<std::basic_string<cha r,std::char_traits<char>,std::allocator<char> >::const_iterator> > >::_Destroy(boost::sub_match<std::basic_string<char,std::char_traits<cha r>,std::allocator<char> >::const_iterator> * _First=0x008d8428, boost::sub_match<std::basic_string<char,std::char_traits<char>,std::allo cator<char> >::const_iterator> * _Last=0x008d8988) Line 787 + 0x11 C++ DtmfGrammarManager.dll!std::vector<boost::sub_match<std::basic_string<ch ar,std::char_traits<char>,std::allocator<char> >::const_iterator>,std::allocator<boost::sub_match<std::basic_string<cha r,std::char_traits<char>,std::allocator<char> >::const_iterator> > >::_Tidy() Line 795 C++ DtmfGrammarManager.dll!std::vector<boost::sub_match<std::basic_string<ch ar,std::char_traits<char>,std::allocator<char> >::const_iterator>,std::allocator<boost::sub_match<std::basic_string<cha r,std::char_traits<char>,std::allocator<char> >::const_iterator> > >::~vector<boost::sub_match<std::basic_string<char,std::char_traits<char >,std::allocator<char> >::const_iterator>,std::allocator<boost::sub_match<std::basic_string<cha r,std::char_traits<char>,std::allocator<char> >::const_iterator> > >() Line 389 C++ DtmfGrammarManager.dll!boost::match_results<std::basic_string<char,std:: char_traits<char>,std::allocator<char> >::const_iterator,std::allocator<boost::sub_match<std::basic_string<char ,std::char_traits<char>,std::allocator<char> >::const_iterator> > >::~match_results<std::basic_string<char,std::char_traits<char>,std::all ocator<char> >::const_iterator,std::allocator<boost::sub_match<std::basic_string<char ,std::char_traits<char>,std::allocator<char> >::const_iterator> > >() Line 74 + 0x3d C++ DtmfGrammarManager.dll!CDtmfGrammar_custom::check(const std::basic_string<char,std::char_traits<char>,std::allocator<char> > & inputData={...}, const std::basic_string<char,std::char_traits<char>,std::allocator<char> > & currentInput={...}, std::basic_string<char,std::char_traits<char>,std::allocator<char> > * pResultValue=0x0012ea9c, const std::basic_string<char,std::char_traits<char>,std::allocator<char> > & termcharArg={...}) Line 949 + 0x19 C++ DtmfGrammarManager.dll!CDtmfGrammarManager::inputUpdate(const char * utterancePortionArg=0x00406e2c) Line 200 + 0x3b C++ mscorwks.dll!7925de73() tg12.exe!feedInput(char* iArg = 0x00406e2c, char* termcharArg = 0x00406e28) Line 22 + 0x1e bytes C++ tg12.exe!main(__int32 argc = 1, char** argv = 0x008d8120) Line 309 + 0x10 bytes C++ tg12.exe!mainCRTStartup() Line 398 + 0xe C ________________________________ <http://www.intervoice.com> Marty Eaves STAFF SOFTWARE ENGINEER CALL PROCESSING & MEDIA SERVICES RESEARCH AND DEVELOPMENT INTERVOICE, INC. P: (972) 454-8348 marty.eaves(a)intervoice.com ________________________________ Intervoice: Connecting People and Information. This e-mail transmission may contain information that is proprietary, privileged and/or confidential and is intended exclusively for the person(s) to whom it is addressed. Any use, copying, retention or disclosure by any person other than the intended recipient or the intended recipient's designees is strictly prohibited. If you are the intended recipient, you must treat the information in confidence and in accordance with all laws related to the privacy and confidentiality of such information. If you are not the intended recipient or their designee, please notify the sender immediately by return e-mail and delete all copies of this email, including all attachments.

2 1

[serialization-1.32.0] de-serializing newer versions that the application can deal with
by Russell Hind 15 Jun '06

15 Jun '06

We have system data written out to an XML archive and being de-serialized at application startup. One object type in the archive we written at version 1 by a newer version of the application. We then ran an older version of the software which only understood version 0 of the object. Does serialization not check the 'BOOST_CLASS_VERSION' of an object before attempting to de-serialize it? If not, how can we access the 'BOOST_CLASS_VERSION' in a serialization member function? I'm looking to do something like this: (this code is just written now so probably is incorrect but hopefully gives the idea). How do we check 'version_of_T' below which should correspond to the BOOST_CLASS_VERSION for T? I'd probably have this only check if the ArchiveT::is_loading::value is true as serializing doesn't matter. The issue at the moment is that an access violation is being thrown which definitely isn't a good idea. I'd like a 'newer object version' exception thrown instead which would enable us to give more useful error information to the user or our error log. Thanks Russell namespace serialization { template <typename T> void check_version(T* Object, unsigned int version)) { if (version_of_T > version) { throw newer_version_exception(); } } } class test { template <typename ArciveT> void serialize(ArchiveT& ar, unsigned int version) { serialization::check_version(this, version); } }; BOOST_CLASS_VERSION(test, 0x00);

3 4