From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27032 invoked by alias); 17 Apr 2007 21:55:07 -0000 Received: (qmail 26936 invoked by uid 48); 17 Apr 2007 21:54:55 -0000 Date: Tue, 17 Apr 2007 21:55:00 -0000 From: "cagney at redhat dot com" To: frysk-bugzilla@sourceware.org Message-ID: <20070417225454.4389.cagney@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug general/4389] New: ptrace in event-loop causes TestBreakpoints inferior to sig-seg-v X-Bugzilla-Reason: AssignedTo Mailing-List: contact frysk-bugzilla-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: frysk-bugzilla-owner@sourceware.org X-SW-Source: 2007-q2/txt/msg00120.txt.bz2 List-Id: 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.