[Bug general/5893] New: fcatch prints stack trace of wrong process

[Bug general/5893] New: fcatch prints stack trace of wrong process

[tromey at redhat dot com]

I ran fcatch on gcc.  gcc forks and execs a child process, cc1.
In my case, cc1 SEGVs -- but fcatch prints a stack trace of the
parent process, gcc.
I don't have an easy way to reproduce this.

-- 
           Summary: fcatch prints stack trace of wrong process
           Product: frysk
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: general
        AssignedTo: frysk-bugzilla at sourceware dot org
        ReportedBy: tromey at redhat dot com


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

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

[Bug general/5893] fcatch prints stack trace of wrong process

[swagiaal at redhat dot com]

------- Additional Comments From swagiaal at redhat dot com  2008-03-11 16:50 -------
Can you please try this again with fcatch from git HEAD.

This should have take care of it:

commit 5492baa03cd955076e3b9cc5305def492de72920
Author: Sami Wagiaalla <swagiaal@redhat.com>
Date:   Mon Mar 10 16:29:44 2008 -0400

    swagiaal: converted fcatch to use ProcRunUtil.
    
    frysk-core/frysk/bindir/ChangeLog
    +2008-03-10  Sami Wagiaalla  <swagiaal@redhat.com>
    +
    +	* fcatch.java: Moved the bulk of the code to FCatch.
    +
    
    frysk-core/frysk/debuginfo/ChangeLog
    +2008-03-10  Sami Wagiaalla  <swagiaal@redhat.com>
    +
    +	* DebugInfoStackFactory.java: Added DEFAULT options.
    +
    
    frysk-core/frysk/util/ChangeLog
    +2008-03-10  Sami Wagiaalla  <swagiaal@redhat.com>
    +
    +	* FCatch.java: Now uses ProcRunUtil.
    +	* TestFCatch.java: Deleted.
    +

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING


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

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

[Bug general/5893] fcatch prints stack trace of wrong process

[tromey at redhat dot com]

------- Additional Comments From tromey at redhat dot com  2008-03-11 19:26 -------
I pulled & rebuilt just now.  Then I tried my test again.
Now I get:

Exception in thread "main" java.lang.NullPointerException
   at frysk.util.FCatch$CatchObserver.updateTerminated(fcatch)
   at frysk.proc.live.LinuxPtraceTask.notifyTerminated(fcatch)
   at frysk.proc.live.LinuxPtraceTaskState.handleAttachedTerminated(fcatch)
   at frysk.proc.live.LinuxPtraceTaskState.access$3(fcatch)
   at frysk.proc.live.LinuxPtraceTaskState$Running.handleTerminatedEvent(fcatch)
   at frysk.proc.live.LinuxPtraceTask.processTerminatedEvent(fcatch)
   at frysk.proc.live.LinuxWaitBuilder.terminated(fcatch)
   at frysk.sys.Wait.wait(fcatch)
   at frysk.sys.Wait.wait(fcatch)
   at frysk.event.WaitEventLoop.block(fcatch)
   at frysk.event.EventLoop.runEventLoop(fcatch)
   at frysk.event.EventLoop.run(fcatch)
   at frysk.util.ProcRunUtil.start(fcatch)
   at frysk.util.FCatch.run(fcatch)
   at frysk.bindir.fcatch.run(fcatch)
   at frysk.bindir.fcatch.main(fcatch)


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW


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

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

[Bug general/5893] fcatch prints stack trace of wrong process

[tromey at redhat dot com]

------- Additional Comments From tromey at redhat dot com  2008-03-11 20:19 -------
FYI -- I updated to this:

2008-03-11  Sami Wagiaalla  <swagiaal@redhat.com>

        * FCatch.java: Remove cached stack trace if     new stack
        trace is available.

and now fcatch does not crash, but it doesn't print a
stack trace either.

-- 


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

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