public inbox for frysk-bugzilla@sourceware.org help / color / mirror / Atom feed
From: "rmoseley at redhat dot com" <sourceware-bugzilla@sourceware.org> To: frysk-bugzilla@sourceware.org Subject: [Bug general/5674] New: frysk does not handle "go" after a "run" command Date: Fri, 25 Jan 2008 20:34:00 -0000 [thread overview] Message-ID: <20080125203404.5674.rmoseley@redhat.com> (raw) Issuing a "go" command right after a "run" command causes a backtrace. Here are the steps to reproduce: (fhpd) load ../pkglibdir/funit-threads-looper Loaded executable file: ../pkglibdir/funit-threads-looper (fhpd) run Attached to process 2484 starting/running with this command: /home/rmoseley/frysk-git1/build/frysk-core/frysk/bindir/../pkglibdir/funit-threads-looper Running process 2484 (fhpd) go Running process 2484 Running process 2484 (fhpd) java.lang.RuntimeException: not added at frysk.proc.live.LinuxPtraceProcState$3.handleDeleteObservation(LinuxPtraceProcState.java:434) at frysk.proc.live.LinuxPtraceProc$14.execute(LinuxPtraceProc.java:660) at frysk.event.EventLoop.runEventLoop(EventLoop.java:372) at frysk.event.EventLoop.run(EventLoop.java:489) fhpd is in an unusable state at this point for most subsequent commands. -- Summary: frysk does not handle "go" after a "run" command Product: frysk Version: unspecified Status: NEW Severity: normal Priority: P2 Component: general AssignedTo: frysk-bugzilla at sourceware dot org ReportedBy: rmoseley at redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=5674 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2008-01-25 20:34 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-01-25 20:34 rmoseley at redhat dot com [this message] 2008-01-30 14:55 ` [Bug general/5674] " rmoseley at redhat dot com
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=20080125203404.5674.rmoseley@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: 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).