[Bug general/4389] New: ptrace in event-loop causes TestBreakpoints inferior to sig-seg-v

["cagney at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

Here is a trace of TestBreakpoints under a merged ptrace/event-loop:


FINE: {frysk.proc.LinuxPtraceTask@37eee0,pid=1569,tid=1569,state=running}
notifyCodeBreakpoint(134,514,608)

17-Apr-07 5:36:20 PM frysk.proc.LinuxPtraceTaskState$Running handleSignaledEvent
FINE: {frysk.proc.LinuxPtraceTask@37eee0,pid=1569,tid=1569,state=running}
handleSignaledEvent, signal: 5

17-Apr-07 5:36:20 PM frysk.proc.Task notifySignaled
FINE: {frysk.proc.LinuxPtraceTask@37eee0,pid=1569,tid=1569,state=running}
notifySignaled(int)

17-Apr-07 5:36:20 PM frysk.proc.LinuxPtraceTask sendContinue
FINE: {frysk.proc.LinuxPtraceTask@37eee0,pid=1569,tid=1569,state=running}
sendContinue

17-Apr-07 5:36:20 PM frysk.proc.LinuxPtraceWaitBuilder getTask
FINE: {TaskId,1569} stopped

17-Apr-07 5:36:20 PM frysk.proc.Host get
FINE: {frysk.proc.LinuxPtraceHost@17f990,state=running} get TaskId

17-Apr-07 5:36:20 PM frysk.proc.LinuxPtraceTaskState$Running handleSignaledEvent
FINE: {frysk.proc.LinuxPtraceTask@37eee0,pid=1569,tid=1569,state=running}
handleSignaledEvent, signal: 11

17-Apr-07 5:36:20 PM frysk.proc.Task notifySignaled
FINE: {frysk.proc.LinuxPtraceTask@37eee0,pid=1569,tid=1569,state=running}
notifySignaled(int)

17-Apr-07 5:36:20 PM frysk.proc.LinuxPtraceTask sendContinue
FINE: {frysk.proc.LinuxPtraceTask@37eee0,pid=1569,tid=1569,state=running}
sendContinue

17-Apr-07 5:36:20 PM frysk.proc.LinuxPtraceWaitBuilder getTask
FINE: {TaskId,1569} exitEvent


and here is the same trace, when the ptrace server is being used:


FINE: {frysk.proc.LinuxPtraceTask@37eee0,pid=1563,tid=1563,state=running}
notifyCodeBreakpoint(134,514,608)

17-Apr-07 5:36:11 PM frysk.proc.LinuxPtraceTaskState$Running handleSignaledEvent
FINE: {frysk.proc.LinuxPtraceTask@37eee0,pid=1563,tid=1563,state=running}
handleSignaledEvent, signal: 5

17-Apr-07 5:36:11 PM frysk.proc.Task notifySignaled
FINE: {frysk.proc.LinuxPtraceTask@37eee0,pid=1563,tid=1563,state=running}
notifySignaled(int)

17-Apr-07 5:36:11 PM frysk.proc.LinuxPtraceTask sendContinue
FINE: {frysk.proc.LinuxPtraceTask@37eee0,pid=1563,tid=1563,state=running}
sendContinue

17-Apr-07 5:36:11 PM frysk.proc.LinuxPtraceWaitBuilder getTask
FINE: {TaskId,1563} stopped

17-Apr-07 5:36:11 PM frysk.proc.Host get
FINE: {frysk.proc.LinuxPtraceHost@17f990,state=running} get TaskId

17-Apr-07 5:36:11 PM frysk.proc.LinuxPtraceTaskState$Running handleTrappedEvent
FINE: {frysk.proc.LinuxPtraceTask@37eee0,pid=1563,tid=1563,state=running}
handleTrappedEvent


Notice how, in the first trace, after the breakpoint has been processed the next
thing back is a signal 11 - sigsegv, while, for the second case, another
breakpoint is seen.

-- 
           Summary: ptrace in event-loop causes TestBreakpoints inferior to
                    sig-seg-v
           Product: frysk
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: general
        AssignedTo: frysk-bugzilla at sourceware dot org
        ReportedBy: cagney at redhat dot com
OtherBugsDependingO 1522
             nThis:


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

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