Red Hat Bugzilla – Bug 590643
Expression parsing improvements: 23x FAIL gdb.cp/realcpp.exp
Last modified: 2016-09-19 22:06:32 EDT
Description of problem: gdb.cp/realcpp.exp was suggested to be run as part of 'Expression Parsing Improvements' feature testing for RHEL6. This testcase has 23 failures across all architectures: Running ./gdb.cp/realcpp.exp ... FAIL: gdb.cp/realcpp.exp: print policyd<base>::policyd FAIL: gdb.cp/realcpp.exp: print policyd<char>::policyd FAIL: gdb.cp/realcpp.exp: print policyd<int>::policyd FAIL: gdb.cp/realcpp.exp: print policyd<long>::policyd FAIL: gdb.cp/realcpp.exp: print policyd<tclass<int> >::policyd FAIL: gdb.cp/realcpp.exp: list base::overload(void) FAIL: gdb.cp/realcpp.exp: list policyd<base>::policyd FAIL: gdb.cp/realcpp.exp: list policyd<char>::policyd FAIL: gdb.cp/realcpp.exp: list policyd<int>::policyd FAIL: gdb.cp/realcpp.exp: list policyd<long>::policyd FAIL: gdb.cp/realcpp.exp: list policyd<tclass<int> >::policyd FAIL: gdb.cp/realcpp.exp: setting breakpoint at base::overload(void) FAIL: gdb.cp/realcpp.exp: continue to base::overload(void) FAIL: gdb.cp/realcpp.exp: setting breakpoint at policyd<base>::policyd FAIL: gdb.cp/realcpp.exp: continue to policyd<base>::policyd FAIL: gdb.cp/realcpp.exp: setting breakpoint at policyd<char>::policyd FAIL: gdb.cp/realcpp.exp: continue to policyd<char>::policyd FAIL: gdb.cp/realcpp.exp: setting breakpoint at policyd<int>::policyd FAIL: gdb.cp/realcpp.exp: continue to policyd<int>::policyd FAIL: gdb.cp/realcpp.exp: setting breakpoint at policyd<long>::policyd FAIL: gdb.cp/realcpp.exp: continue to policyd<long>::policyd FAIL: gdb.cp/realcpp.exp: setting breakpoint at policyd<tclass<int> >::policyd FAIL: gdb.cp/realcpp.exp: continue to policyd<tclass<int> >::policyd Version-Release number of selected component (if applicable): gdb-7.1-18 How reproducible: always Steps to Reproduce: 1. runtest --tool=gdb gdb.cp/realcpp.ex 2. 3. Actual results: # of expected passes 376 # of unexpected failures 23 Expected results: # of expected passes 399 Additional info:
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion.
Hi Keith, I believe you should be aware of it - do you agree with these FAILures?
Yes, this is expected. IMO, we should retire realecpp.exp in favor of the upstream cpexprs.exp (which is probably already included). realcpp and cpexprs are essentially identical; the failing default template tests -- 20 of the failures in realcpp -- are not included in cpexprs.exp because there is no way to fix them today. That leaves the three known failures (which I believe can be fixed) which also occur in realcpp: "print"/"list"/"break" & "continue" to base::overload(void) [which is declared const, but gdb doesn't recognize that].
Therefore closing as known FAILs which are common in GDB.