From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26041 invoked by alias); 3 Aug 2007 12:57:55 -0000 Received: (qmail 26011 invoked by uid 48); 3 Aug 2007 12:57:45 -0000 Date: Fri, 03 Aug 2007 12:57:00 -0000 Message-ID: <20070803125745.26010.qmail@sourceware.org> From: "mark at klomp dot org" To: frysk-bugzilla@sourceware.org In-Reply-To: <20070803122627.4889.pmachata@redhat.com> References: <20070803122627.4889.pmachata@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug general/4889] adding new codeObserver in updateHit causes java.lang.IllegalStateException: Already stepping 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-q3/txt/msg00254.txt.bz2 List-Id: ------- Additional Comments From mark at klomp dot org 2007-08-03 12:57 ------- This is related/similar to bug #4747 with the difference that frysk itself is responsible for generating the stop signal to install the breakpoint instead of an external trigger. This will be fixed with the fix for #4747. The "workaround": task.requestAddCodeObserver(observer, address); task.requestUnblock(this); return Action.BLOCK; Is most likely what you actually want. It makes sure that the observer is installed and only after that the task is unblocked. If you use the sequence: task.requestAddCodeObserver(observer, address); return Action.CONTINUE; The request to add the new observer is only pending and the task might already be running long before the observer is installed (so you could miss hitting that breakpoint). This is actually what is happening here. -- http://sourceware.org/bugzilla/show_bug.cgi?id=4889 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.