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/6695] New: attaching and then killing process causes stacktrace Date: Wed, 25 Jun 2008 15:56:00 -0000 [thread overview] Message-ID: <20080625155521.6695.rmoseley@redhat.com> (raw) Attaching to a process and then killing it causes a stacktrace in both the UI and on the command line: Exception in thread "main" java.lang.RuntimeException: {frysk.proc.live.LinuxPtraceTask@5b21755f,pid=19574,tid=19574,state=destroyed} in state "destroyed" did not handle handleStoppedEvent SIGSTOP(19) at frysk.proc.live.State.unhandled(State.java:67) at frysk.proc.live.LinuxPtraceTaskState.handleStoppedEvent(LinuxPtraceTaskState.java:71) at frysk.proc.live.LinuxPtraceTask.processStoppedEvent(LinuxPtraceTask.java:226) at frysk.proc.live.LinuxWaitBuilder.stopped(LinuxWaitBuilder.java:202) at frysk.sys.Wait.wait(Wait.cxx:586) at frysk.sys.Wait.wait(Wait.java:126) at frysk.event.WaitEventLoop.block(WaitEventLoop.java:81) at frysk.event.EventLoop.runEventLoop(EventLoop.java:372) at frysk.event.EventLoop.run(EventLoop.java:482) at frysk.bindir.fhpd.main(fhpd.java:186) and here is the stack trace from the UI: {frysk.proc.live.LinuxPtraceProc@665bad3e,pid=20304,state=running} in state "running" did not handle handleRemoval java.lang.RuntimeException: {frysk.proc.live.LinuxPtraceProc@665bad3e,pid=20304,state=running} in state "running" did not handle handleRemoval at frysk.proc.live.State.unhandled(State.java:67) at frysk.proc.live.LinuxPtraceProcState.handleRemoval(LinuxPtraceProcState.java:62) at frysk.proc.live.LinuxPtraceProc$1.execute(LinuxPtraceProc.java:332) at frysk.event.EventLoop.runEventLoop(EventLoop.java:365) at frysk.event.EventLoop.run(EventLoop.java:482) at frysk.gui.Gui$5.run(Gui.java:355) at java.lang.Thread.run(libgcj.so.8rh) -- Summary: attaching and then killing process causes stacktrace 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 OtherBugsDependingO 1633,2246 nThis: http://sourceware.org/bugzilla/show_bug.cgi?id=6695 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
reply other threads:[~2008-06-25 15:56 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080625155521.6695.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).