[Bug general/3910] New: Under 2.6.18-1.3002.el5 ProcBlockAction stalls (forever) with a proc object that has had assertSendStop() called

[Bug general/3910] New: Under 2.6.18-1.3002.el5 ProcBlockAction stalls (forever) with a proc object that has had assertSendStop() called

[pmuldoon at redhat dot com]

Basically

...
...
// Get a Proc
    AckProcess ackProc = new DetachedAckProcess();
    ackProc.assertSendStop();

...
...

In a class that extends ProcBlockAction, the constructor is called, but the the
overriden existingTask() method never gets called. It seems hang somewere. 

Like

Class Foo extends ProcBlockAction

public Foo(Proc proc)
{
   super(proc)
   ..
   // do constructor stuff
   ..
}

public void existingTask (Task task)
{
...
// This never gets called. No tasks are collected?
}

Apologies at the lack of initial data, just wanted to get the bug filed, and add
data later

-- 
           Summary: Under 2.6.18-1.3002.el5 ProcBlockAction stalls (forever)
                    with a proc object that has had assertSendStop() called
           Product: frysk
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: general
        AssignedTo: frysk-bugzilla at sourceware dot org
        ReportedBy: pmuldoon at redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=3910

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug general/3910] Under 2.6.18-1.3002.el5 ProcBlockAction stalls (forever) with a proc object that has had assertSendStop() called

[pmuldoon at redhat dot com]

------- Additional Comments From pmuldoon at redhat dot com  2007-01-25 22:21 -------
Adding logs and run scenario:

TestRunner --timeout 5 -log frysk=FINE frysk.util.TestFCore.testCoreFileCreated

Running testCoreFileCreated(frysk.util.TestFCore) ...23254.23254:
argv[0]=/home/pmuldoon/frysk_bin/frysk-core/frysk/pkglibdir/funit-child
23254.23254: argv[1]=--wait=suspend
23254.23254: argv[2]=10
23254.23254: argv[3]=23252
23254.23254: starting 23254
23254.23254: new thread 23254.23254
23254.23254: notify 23252 with 10 (User defined signal 1) -- new thread 23254.23254

FAIL
  junit.framework.AssertionFailedError: event loop run explictly stopped
(Running event loop for core file)

Time: 25.015

There was 1 failure:
1)
testCoreFileCreated(frysk.util.TestFCore)junit.framework.AssertionFailedError:
event loop run explictly stopped (Running event loop for core file)
   at frysk.proc.TestLib.assertRunUntilStop(TestRunner)
   at frysk.proc.TestLib.assertRunUntilStop(TestRunner)
   at frysk.util.TestFCore.constructCore(TestRunner)
   at frysk.util.TestFCore.testCoreFileCreated(TestRunner)
   at frysk.junit.Runner.runCases(TestRunner)
   at frysk.junit.Runner.runArchCases(TestRunner)
   at frysk.junit.Runner.runTestCases(TestRunner)
   at TestRunner.main(TestRunner)

FAILURES!!!
Tests run: 1,  Failures: 1,  Errors: 0

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=3910

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug general/3910] Under 2.6.18-1.3002.el5 ProcBlockAction stalls (forever) with a proc object that has had assertSendStop() called

[pmuldoon at redhat dot com]

------- Additional Comments From pmuldoon at redhat dot com  2007-01-25 22:25 -------
Created an attachment (id=1522)
 --> (http://sourceware.org/bugzilla/attachment.cgi?id=1522&action=view)
Core event log


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=3910

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug general/3910] Under 2.6.18-1.3002.el5 ProcBlockAction stalls (forever) with a proc object that has had assertSendStop() called

[cagney at redhat dot com]

------- Additional Comments From cagney at redhat dot com  2007-01-26 22:51 -------
{frysk.proc.LinuxPtraceTask@1dcf50,pid=23254,tid=23254,state=detached} handleAttach
{frysk.proc.LinuxPtraceTask@1dcf50,pid=23254,tid=23254,state=detached} sendAttach
{frysk.proc.LinuxPtraceProc@172140,pid=23254,oldState=Attaching.ToMainTask}
handleAddObservation
{frysk.proc.LinuxPtraceHost$PollWaitOnSigChld@1a6ab0,sig=Sig_CHLD} execute
frysk.sys.Wait pid 0 errno 0 (Success)
{frysk.proc.LinuxPtraceHost$PollWaitOnSigChld@1a6ab0,sig=Sig_CHLD} execute
frysk.sys.Wait pid 0 errno 0 (Success)

This is an attempt at starting an attatch.  sendAttach==ptrace(PT_ATTACH), then
it gets two SIGCHLD's but waitpid returns zip on both occasions.

Is this a child process or daemon process - might affect things.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |cagney at redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=3910

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug general/3910] Under 2.6.18-1.3002.el5 ProcBlockAction stalls (forever) with a proc object that has had assertSendStop() called

[pmuldoon at redhat dot com]

------- Additional Comments From pmuldoon at redhat dot com  2007-01-29 15:45 -------
The child is started with DetachedAckProcess().

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=3910

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.