[xpressive] HP-UX_ia64_aCC problem ... care to help?
Two of xpressive's tests are crashing on the HP-UX_ia64_aCC platform. Is there anybody with access to this platform that would like to help me track it down? Just run xpressive's "test_actions" test and send me a backtrace of the crash. Whoever helps gets a gold star. :-) -- Eric Niebler Boost Consulting www.boost-consulting.com
Eric Niebler wrote:
Just run xpressive's "test_actions" test and send me a backtrace of the crash.
Full test run just completed and this test, as well as test_symbols, failed because of a missing header file: <boost/fusion/sequence/view/iterator_range/detail/value_at_impl.hpp> bash-2.03$ find . -name "*.xml" -exec grep -l value_at_impl.hpp {} \; ./test_actions.test/acc/debug/link-static/test_log.xml ./test_symbols.test/acc/debug/link-static/test_log.xml bash-2.03$ This is a known issue and, I thought, it was fixed. In fact, the report dated Tue, 2 Oct 2007 03:32:23 +0000 has test_actions exiting with "memory access violation". boost-trunk.tar.bz2 is dated 08:36 Eastern time. I'm not sure what's going on with the tarball. I'll get missing files from SVN and run the test, later today or tomorrow. Thanks, Boris ----- Original Message ----- From: "Eric Niebler" <eric@boost-consulting.com> To: "Boost mailing list" <boost@lists.boost.org> Sent: Tuesday, October 02, 2007 4:01 PM Subject: [boost] [xpressive] HP-UX_ia64_aCC problem ... care to help?
Two of xpressive's tests are crashing on the HP-UX_ia64_aCC platform. Is there anybody with access to this platform that would like to help me track it down? Just run xpressive's "test_actions" test and send me a backtrace of the crash. Whoever helps gets a gold star. :-)
-- Eric Niebler Boost Consulting www.boost-consulting.com _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
test_actions crashes when std::string is trying to dereference _C_data member which happens to be zero. It happens inside regex_match(). Attached slightly reduced reproducer. test_symbols.cpp has a similar call to regex_match() and I'm sure it crashes for the same reason. Just rearranging the code in RW library <string> header makes the crash disappear which may be indicative of a code generation problem. And everything is fine when compiling with g++ 4.2.1. I suggest, unless you have a reason to believe that it may be some code in xpressive that is causing the problem, we treat these test failures as aC++ code generation problem at this point. We'll investigate it and report back. #include <boost/xpressive/xpressive_static.hpp> #include <boost/xpressive/regex_actions.hpp> extern "C" int puts(const char*); namespace xp = boost::xpressive; int main() { using namespace boost::xpressive; std::string result; std::string str("foo bar"); sregex rx = (+_w)[ xp::ref(result) += _ ] >> *(' ' >> (+_w)[ xp::ref(result) += ',' + _ ]); puts("calling regex_match"); regex_match(str, rx); puts("exiting"); } Thanks, Boris ----- Original Message ----- From: "Eric Niebler" <eric@boost-consulting.com> To: "Boost mailing list" <boost@lists.boost.org> Sent: Tuesday, October 02, 2007 4:01 PM Subject: [boost] [xpressive] HP-UX_ia64_aCC problem ... care to help?
Two of xpressive's tests are crashing on the HP-UX_ia64_aCC platform. Is there anybody with access to this platform that would like to help me track it down? Just run xpressive's "test_actions" test and send me a backtrace of the crash. Whoever helps gets a gold star. :-)
-- Eric Niebler Boost Consulting www.boost-consulting.com _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Boris Gubenko wrote:
test_actions crashes when std::string is trying to dereference _C_data member which happens to be zero. It happens inside regex_match(). Attached slightly reduced reproducer.
test_symbols.cpp has a similar call to regex_match() and I'm sure it crashes for the same reason.
Just rearranging the code in RW library <string> header makes the crash disappear which may be indicative of a code generation problem. And everything is fine when compiling with g++ 4.2.1.
I suggest, unless you have a reason to believe that it may be some code in xpressive that is causing the problem, we treat these test failures as aC++ code generation problem at this point. We'll investigate it and report back.
Wow, you mean I don't have to do anything? That's great! :-) Thanks for investigating this, Boris. Let me know what you find out. -- Eric Niebler Boost Consulting www.boost-consulting.com
Boris Gubenko wrote:
test_actions crashes when std::string is trying to dereference _C_data member which happens to be zero. It happens inside regex_match(). Attached slightly reduced reproducer.
test_symbols.cpp has a similar call to regex_match() and I'm sure it crashes for the same reason.
Just rearranging the code in RW library <string> header makes the crash disappear which may be indicative of a code generation problem. And everything is fine when compiling with g++ 4.2.1.
I suggest, unless you have a reason to believe that it may be some code in xpressive that is causing the problem, we treat these test failures as aC++ code generation problem at this point. We'll investigate it and report back.
#include <boost/xpressive/xpressive_static.hpp> #include <boost/xpressive/regex_actions.hpp> extern "C" int puts(const char*);
namespace xp = boost::xpressive;
int main() { using namespace boost::xpressive;
std::string result; std::string str("foo bar"); sregex rx = (+_w)[ xp::ref(result) += _ ] >> *(' ' >> (+_w)[ xp::ref(result) += ',' + _ ]); puts("calling regex_match"); regex_match(str, rx); puts("exiting"); }
Hi, Boris. Is there any news about this issue? Can you suggest a work-around or should I mark these failures expected? -- Eric Niebler Boost Consulting www.boost-consulting.com
Eric Niebler wrote:
Hi, Boris. Is there any news about this issue? Can you suggest a work-around or should I mark these failures expected?
Hi, Eric. No progress, sorry. Did not have any chance to look at this. I think that marking these failures expected with a comment like (stolen from John Maddock) "These test failures are reported to be under investigation at HP's compiler lab" is the right thing to do. Please be assured that this issue is not forgotten and when I have anything to report, I'll do so. Thanks, Boris ----- Original Message ----- From: "Eric Niebler" <eric@boost-consulting.com> To: <boost@lists.boost.org> Cc: "Boris Gubenko" <Boris.Gubenko@hp.com> Sent: Tuesday, October 16, 2007 7:49 PM Subject: Re: [boost] [xpressive] HP-UX_ia64_aCC problem ... care to help?
Boris Gubenko wrote:
test_actions crashes when std::string is trying to dereference _C_data member which happens to be zero. It happens inside regex_match(). Attached slightly reduced reproducer.
test_symbols.cpp has a similar call to regex_match() and I'm sure it crashes for the same reason.
Just rearranging the code in RW library <string> header makes the crash disappear which may be indicative of a code generation problem. And everything is fine when compiling with g++ 4.2.1.
I suggest, unless you have a reason to believe that it may be some code in xpressive that is causing the problem, we treat these test failures as aC++ code generation problem at this point. We'll investigate it and report back.
#include <boost/xpressive/xpressive_static.hpp> #include <boost/xpressive/regex_actions.hpp> extern "C" int puts(const char*);
namespace xp = boost::xpressive;
int main() { using namespace boost::xpressive;
std::string result; std::string str("foo bar"); sregex rx = (+_w)[ xp::ref(result) += _ ] >> *(' ' >> (+_w)[ xp::ref(result) += ',' + _ ]); puts("calling regex_match"); regex_match(str, rx); puts("exiting"); }
Hi, Boris. Is there any news about this issue? Can you suggest a work-around or should I mark these failures expected?
-- Eric Niebler Boost Consulting www.boost-consulting.com _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
participants (2)
-
Boris Gubenko -
Eric Niebler