RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 590643 - Expression parsing improvements: 23x FAIL gdb.cp/realcpp.exp
Summary: Expression parsing improvements: 23x FAIL gdb.cp/realcpp.exp
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gdb
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Jan Kratochvil
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-10 12:01 UTC by Petr Muller
Modified: 2016-09-20 02:06 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-11 19:26:40 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Petr Muller 2010-05-10 12:01:32 UTC 
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:
Comment 1 RHEL Program Management 2010-05-10 13:24:18 UTC 
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.
Comment 3 Jan Kratochvil 2010-05-11 19:02:43 UTC 
Hi Keith, I believe you should be aware of it - do you agree with these FAILures?
Comment 4 Keith Seitz 2010-05-11 19:13:20 UTC 
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].
Comment 5 Jan Kratochvil 2010-05-11 19:26:40 UTC 
Therefore closing as known FAILs which are common in GDB.
Note You need to log in before you can comment on or make changes to this bug.