public inbox for frysk-bugzilla@sourceware.org help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org> To: frysk-bugzilla@sourceware.org Subject: [Bug general/4889] adding new codeObserver in updateHit causes java.lang.IllegalStateException: Already stepping Date: Fri, 03 Aug 2007 12:57:00 -0000 [thread overview] Message-ID: <20070803125745.26010.qmail@sourceware.org> (raw) In-Reply-To: <20070803122627.4889.pmachata@redhat.com> ------- 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.
next prev parent reply other threads:[~2007-08-03 12:57 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-08-03 12:26 [Bug general/4889] New: " pmachata at redhat dot com 2007-08-03 12:57 ` mark at klomp dot org [this message] 2007-08-10 11:23 ` [Bug general/4889] " mark at klomp dot org 2007-08-15 11:08 ` mark at klomp dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20070803125745.26010.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=frysk-bugzilla@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).