From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20639 invoked by alias); 6 Aug 2007 13:18:43 -0000 Received: (qmail 19260 invoked by uid 48); 6 Aug 2007 13:18:32 -0000 Date: Mon, 06 Aug 2007 13:18:00 -0000 Message-ID: <20070806131832.19256.qmail@sourceware.org> From: "mark at klomp dot org" To: frysk-bugzilla@sourceware.org In-Reply-To: <20070803222249.4894.pmachata@redhat.com> References: <20070803222249.4894.pmachata@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug general/4894] "java.lang.RuntimeException: not added" when removing codeObserver inside its own handler 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/msg00265.txt.bz2 List-Id: ------- Additional Comments From mark at klomp dot org 2007-08-06 13:18 ------- Thanks for the testcase. Code observers can be added multiple times for different addresses (as you do in this test case). But Proc doesn't know about this and treats the double add and one delete as if the Code observer should be deleted completely, so if you delete it for the other address the Proc sanity check kicks in and flags it as a double delete. Quick workaround for now is to create different Code observers for different addresses. -- http://sourceware.org/bugzilla/show_bug.cgi?id=4894 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.