public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
From: "pmachata at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Subject: [Bug general/4889] New: adding new codeObserver in updateHit causes java.lang.IllegalStateException: Already stepping
Date: Fri, 03 Aug 2007 12:26:00 -0000	[thread overview]
Message-ID: <20070803122627.4889.pmachata@redhat.com> (raw)

FC6.

Adding new codeObserver in updateHit causes java.lang.IllegalStateException:
Already stepping.  The stack trace I'm getting:
Exception in thread "main" java.lang.IllegalStateException: Already stepping
   at frysk.proc.Breakpoint.prepareStep(fltrace)
   at frysk.proc.live.LinuxTaskState$Running.sendContinue(fltrace)
   at frysk.proc.live.LinuxTaskState$Running.handleStoppedEvent(fltrace)
   at frysk.proc.live.LinuxTask.processStoppedEvent(fltrace)
   at frysk.proc.live.LinuxWaitBuilder.stopped(fltrace)
   at frysk.sys.Wait.wait(fltrace)
   at frysk.sys.Wait.waitAll(fltrace)
   at frysk.event.WaitEventLoop.block(fltrace)
   at frysk.event.EventLoop.runEventLoop(fltrace)
   at frysk.event.EventLoop.run(fltrace)
   at frysk.util.Ltrace.trace(fltrace)
   at frysk.bindir.fltrace.run(fltrace)
   at frysk.bindir.fltrace.main(fltrace)

This doesn't seem to happen when requesting observation of already observed
state.  The problem also goes away when I do

      task.requestUnblock(this);
      return Action.BLOCK;

intead of return Action.CONTINUE.  The problem also went away when something
like that was in effect:

      task.getProc().getMainTask().requestAddCodeObserver(this, retAddr);
      System.err.println("[" + task.getTaskId().intValue() + "]");

All this seems to point to the problem of frysk having "enough time" to do the
observer shenanigans, as is suggested by comments on several places.

`retAddr' given above could have been arbitrary, e.g. I tried to enter
0x080483b4, the address of main in my testing binary, so the problems wasn't in
that I'd request breakpoint inside data segment or something.

-- 
           Summary: adding new codeObserver in updateHit causes
                    java.lang.IllegalStateException: Already stepping
           Product: frysk
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: general
        AssignedTo: frysk-bugzilla at sourceware dot org
        ReportedBy: pmachata at redhat dot com
  GCC host triplet: i686-pc-linux-gnu
OtherBugsDependingO 2229
             nThis:


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.


             reply	other threads:[~2007-08-03 12:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-03 12:26 pmachata at redhat dot com [this message]
2007-08-03 12:57 ` [Bug general/4889] " mark at klomp dot org
2007-08-10 11:23 ` 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=20070803122627.4889.pmachata@redhat.com \
    --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: link
Be 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).