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.

Description of problem:
gdb.mi/mi-nsmoribund.exp testcase was suggested to be run as part of 'Asynchronous interaction' feature testing for RHEL6. This testcase has one FAIL across all architectures: 

Running ./gdb.mi/mi-nsmoribund.exp ...
FAIL: gdb.mi/mi-nsmoribund.exp: unexpected stop

I don't think this is really important, I'm reporting it for the sake of completeness so it can be evaluated.

Version-Release number of selected component (if applicable):
gdb-7.1-18.el6

How reproducible:
always

Steps to Reproduce:
1. runtest --tool=gdb gdb.mi/mi-nsmoribund.exp
  
Actual results:
# of expected passes            20
# of unexpected failures        1

Expected results:
# of expected passes            21

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.

As a gross hack I can just increase the moribunds liveness:
              old_loc->events_till_retirement = 3 * (thread_count () + 1);

which makes the problem no longer practically reproducible.  The right fix to be discussed upstream.

Thanks, it could be a needless "stopper of the non-stop mode".

gdb-7.1-19.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/gdb-7.1-19.fc13

gdb-7.1-19.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

# runtest --tool=gdb gdb.mi/mi-nsmoribund.exp
(...)
                === gdb Summary ===

# of expected passes            21

Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.