Greetings I've just emerged (I'm using gentoo) boost, once using bjam and another time without it. In both cases (not that it could make a difference) I just can't get the boost_regex to work. It blows... After compiling a few examples (captures_example, and grep) in both my home and work pc. I get the same result... segmentation fault. While running captures_example in the line std::cout << " $" << i << " = \"" << what[i] << "\"\n"; After doing some debug, I was able to find only the consequence. (I didn't search that hard...) In sub_match.hpp:73 result.append(1, *i); the value of i is 0x1<address out of bounds>. the line match_results.hpp:123 supposly returns const boost::sub_match<__gnu_cxx::__normal_iterator<char const*, std::string> > &) @0x804ded8: {<std::pair<__gnu_cxx::__normal_iterator<char const*, std::string>, __gnu_cxx::__normal_iterator<char const*, std::string> >> = { first = {<std::iterator<std::random_access_iterator_tag, char, int, char const*, char const&>> = {<No data fields>}, _M_current = 0x1 <Address 0x1 out of bounds>}, second = {<std::iterator<std::random_access_iterator_tag, char, int, char const*, char const&>> = {<No data fields>}, _M_current = 0x804d067 "eeeeeeee"}}, matched = 111, m_captures = {ptr = 0x1}} strangely enough, in the debuger, after returning from line match_results.hpp:123 the execution jumps to match_results.hpp:125 and return return m_null; but the cpu registers don't change... the truth is that I get this Program received signal SIGSEGV, Segmentation fault. 0x0804a6d6 in boost::sub_match<__gnu_cxx::__normal_iterator<char const*, std::string> >::str ( this=0x804ded8) at sub_match.hpp:73 73 result.append(1, *i); for no apparent reason. Any ideas? I'm using gcc 4.1 in my home pc and gcc 3.3.6 in my office pc. PIII800MHz and PIV1.5GHz both with 512MB ram. ___________________________________________________________________ O SAPO já está livre de vírus com a Panda Software, fique você também! Clique em: http://antivirus.sapo.pt