This is the mail archive of the
frysk@sources.redhat.com
mailing list for the frysk project.
Re: frysk-core/frysk/proc ChangeLog TaskState.java
- From: Sami Wagiaalla <swagiaal at redhat dot com>
- To: frysk at sourceware dot org, swagiaal at redhat dot com
- Date: Fri, 25 Aug 2006 11:54:15 -0400
- Subject: Re: frysk-core/frysk/proc ChangeLog TaskState.java
- References: <20060825015010.GA9037@GreenHouse.cn.ibm.com>
Yao Qi wrote:
Log message:
2006-08-24 <swagiaal@redhat.com>
Hi, Sami,
The name in ChangeLog entry is lost, and I have add it for you. :)
Thanx... i must have forgotten to add the change log to the patch i
applied :)
* TaskState.java: Added handleSignaledEvent to runningInSyscall
Could you explain why do you do this? I am confused by this a bit.
Do you mean the child will receive a signal when it is in syscall?
Is there any bugs opened before we apply this patch?
The reason is that on RHEL4 we were getting this error with all the
tests that
used the system calls code.
java.lang.RuntimeException:
{frysk.proc.LinuxTask@4fa960,pid=10898,tid=10898,state=runningInSyscall}
in state "runningInSyscall" did not handle handleSignaledEvent
this is on the following kernel:
+ uname -a
Linux hs20-bc2-3.build.redhat.com 2.6.9-34.ELsmp #1 SMP Fri Feb 24
16:56:28 EST 2006 i686 i686 i386 GNU/Linux
I have not had a chance to reseach it more. I wanted to get the patch in
for the release. The truth is even if it is some
kind of kernel bug it is not likely to get fixed and we will have to
handle it in the same way that the patch did :)
I'll know more soon :)