From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9819 invoked by alias); 20 Jun 2007 15:19:04 -0000 Received: (qmail 9783 invoked by uid 48); 20 Jun 2007 15:18:55 -0000 Date: Wed, 20 Jun 2007 15:19:00 -0000 Message-ID: <20070620151855.9782.qmail@sourceware.org> From: "mark at klomp dot org" To: frysk-bugzilla@sourceware.org In-Reply-To: <20070619210613.4663.mcvet@redhat.com> References: <20070619210613.4663.mcvet@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug general/4663] TaskObserver.Instruction doesn't appear to unblock on new process' first instructions 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/msg00343.txt.bz2 List-Id: ------- Additional Comments From mark at klomp dot org 2007-06-20 15:18 ------- Added a simplified test and a first workaround for this issue. 2007-06-20 Mark Wielaard * frysk-core/frysk/proc/Observation.java (toString): Include observable and observer. * frysk-core/frysk/proc/Task.java (just_started): New boolean field. * frysk-core/frysk/proc/TestTaskObserverInstruction.java (testFirstInstructionStep): New test) (StepAttachedObserver): New inner class. (testFirstInstructionSteppingEngine): Renamed method from testFirstInstructionStep. Remove broken marker. 2007-06-20 Mark Wielaard * frysk-core/frysk/proc/ptrace/LinuxTaskState.java (blockOrAttachContinue): Set just_started marker. (sendContinue): Reset just_started marker unless first step. (Running.handleTrapped): Check and reset just_started marker. Keeping open to resolve with a real Stepping state and after consulting on other debug step marker corner cases. -- What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|frysk-bugzilla at sourceware|mark at klomp dot org |dot org | Status|NEW |ASSIGNED http://sourceware.org/bugzilla/show_bug.cgi?id=4663 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.