SEG Escalation Template

All Issues: Problem Description
---------------------------------------------------
1. Time and date of problem: Reported 01-22-2010 12:06pm JST
2. System architecture(s): ia64
3. Provide a clear and concise problem description as it is understood at the
  time of escalation. Please be as specific as possible in your description.
  Do not use the generic term "hang", as that can mean many things.
  Observed behavior:
  Desired behavior:
This is a REGRESSION from strace-4.5.16-1.el4_8.2.
The advisory number is RHBA-2009:1175-1.

This issue occurred strace-4.5.16-1.el4_8.6.
The advisory number is RHBA-2009:1644-1.

When strace is executed multiple times concurrently, strace sometimes
stops logging a trace and never restarts.
As a result, the trace logs of some target process can not be got correctly.

This issue occurs frequently.

Then, the return code of any function logged in the trace is unexpected value.
For example, the return code of uname() in the log below is -922337203685477580
while it should be -1 or 0 according to the manual page of uname(2).

===
13280 execve(0x600000000001b3f0, [0], [/* 0 vars */]) = -1
13280 uname({sys="Linux", node="localhost.localdomain", ...}) = -922337203685477
5808
13280 brk(0)                            = 0xffffffffffffffff
13280 access("/etc/ld.so.preload", R_OK) = -1
13280 open("/etc/ld.so.cache", O_RDONLY) = -9223372036854775808
13280 fstat(3, {st_mode=S_IFREG|0644, st_size=44912, ...}) = -922337203685477580
8
13280 mmap(NULL, 44912, PROT_READ, MAP_PRIVATE, 3, 0) = 0x8000000000000000
13280 close(3)
...snip...
===

The process of strace stops at wait() system call.


Version-Release number of selected component:
Red Hat Enterprise Linux Version Number: 4.8
Release Number: GA
Architecture: ia64
Kernel Version: 2.6.9-89.0.19.EL
Related Package Version: strace-4.5.16-1.el4_8.6
Related Middleware/Application: none

Drivers or hardware or architecture dependency:
unknown

How reproducible:
frequently


Actual Results:
strace stops logging.

===The following is result log===
[root@localhost testpro2]# ./test2.sh
*** start strace No.0 pid:17096 ***
*** start strace No.1 pid:17137 ***
*** start strace No.2 pid:17171 ***
(snip)
*** start strace No.17 pid:18416 ***
*** start strace No.18 pid:18679 ***
*** start strace No.19 pid:18682 ***
[root@localhost testpro2]# ls -l log_*
-rw-r--r--  1 root root 418785 Jan 20 01:30 log_0
-rw-r--r--  1 root root 453963 Jan 20 01:30 log_1
(snip)
-rw-r--r--  1 root root 440642 Jan 20 01:30 log_3
-rw-r--r--  1 root root  53927 Jan 20 01:30 log_4
-rw-r--r--  1 root root 442178 Jan 20 01:30 log_5
-rw-r--r--  1 root root  53927 Jan 20 01:30 log_6
-rw-r--r--  1 root root 458201 Jan 20 01:30 log_7
-rw-r--r--  1 root root 445321 Jan 20 01:30 log_8
-rw-r--r--  1 root root 415137 Jan 20 01:30 log_9
[root@localhost testpro2]# ls -l log_*            ... After a few seconds
-rw-r--r--  1 root root 738629 Jan 20 01:30 log_0
-rw-r--r--  1 root root 748487 Jan 20 01:30 log_1
(snip)
-rw-r--r--  1 root root 738781 Jan 20 01:30 log_3
-rw-r--r--  1 root root  53927 Jan 20 01:30 log_4 ... This trace logs stop.
-rw-r--r--  1 root root 740156 Jan 20 01:30 log_5
-rw-r--r--  1 root root  53927 Jan 20 01:30 log_6 ... This trace logs stop.
-rw-r--r--  1 root root 733237 Jan 20 01:30 log_7
-rw-r--r--  1 root root 721511 Jan 20 01:30 log_8
-rw-r--r--  1 root root 709681 Jan 20 01:30 log_9
[root@localhost testpro2]#
===============================================

Expected Results:
strace completes logging the trace.


4. Specific action requested of SEG:
Could you please investigate the issue? This is reported as a regression issue.

5. Is a defect (bug) in the product suspected? yes/no
  Bugzilla number (if one already exists):
None

6. Does a proposed patch exist? yes/no
  If yes, attach patch, making sure it is in unified diff format (diff -pruN)
No

7. What is the impact to the customer when they experience this problem?
Business Impact:
This issue is a REGRESSION issue from strace-4.5.16-1.el4_8.2.