Bug 245440

Summary:	Spurious testcase FAIL: gdb.base/attach.exp: after attach3, exit (timeout)
Product:	Red Hat Enterprise Linux 5	Reporter:	Jan Kratochvil <jan.kratochvil>
Component:	gdb	Assignee:	Jan Kratochvil <jan.kratochvil>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	5.0	CC:	cagney
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-01-14 10:34:35 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:	233853
Bug Blocks:

Description Jan Kratochvil 2007-06-23 09:06:17 UTC

Description of problem:
This testcase was always a race with spurious results.
On a change
* Tue Jun 19 2007 Jan Kratochvil <jan.kratochvil> - 6.5-19
- Fix attaching to stopped processes / pending signals (BZ 209521, 233853).
the probability of FAIL got higher.

Version-Release number of selected component (if applicable):
gdb-6.5-19.el5

How reproducible:
Rarely.

Steps to Reproduce:
1. runtest gdb.base/attach.exp

Actual results:
FAIL: gdb.base/attach.exp: after attach3, exit (timeout)

Expected results:
PASS: gdb.base/attach.exp: after attach3, exit

Additional info:
It was found there occurs:
ptrace(PTRACE_KILL,PID)
waitpid(pid)==pid
waitpid(pid) -> HANGS
The second waitpid should not be called there.

Comment 1 Jan Kratochvil 2007-06-23 09:24:04 UTC

Probably the same reason is for:
FAIL: gdb.pie/attach.exp: (timeout) after attach3, exit

Comment 2 Jan Kratochvil 2008-01-14 10:34:35 UTC

This problem is no longer seen neither in Brew nor in RHTS, older logs were
deleted.  Expecting a consequence of the inappropriate and/or utrace-buggy
kernels in Brew but I did not check it more.