Bug 590623
Summary: | Asynchronous interaction: FAIL: gdb.mi/mi-nsmoribund.exp | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Petr Muller <pmuller> |
Component: | gdb | Assignee: | Jan Kratochvil <jan.kratochvil> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Petr Muller <pmuller> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 6.0 | CC: | cagney, ebachalo, ohudlick |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | gdb-7.1-19.el6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-11-10 20:26:03 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 519853 |
Description
Petr Muller
2010-05-10 11:01:28 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. 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. |