public inbox for frysk-bugzilla@sourceware.org help / color / mirror / Atom feed
From: "mcvet at redhat dot com" <sourceware-bugzilla@sourceware.org> To: frysk-bugzilla@sourceware.org Subject: [Bug general/4260] New: ptrace complains about monitor stack tracing Date: Thu, 22 Mar 2007 15:38:00 -0000 [thread overview] Message-ID: <20070322153757.4260.mcvet@redhat.com> (raw) With terminating, fork, exec and clone observers on nautilus, and then making it fork, it prints into the background: Call stack is broken - couldn't unwind! ptrace: No such process at frysk.sys.Errno.throwErrno(FryskGui) at frysk.sys.Ptrace$PtraceThread.notifyPtraceThread(FryskGui) at frysk.sys.Ptrace.peekRegisters(FryskGui) at frysk.sys.RegisterSetBuffer.refresh(FryskGui) at frysk.sys.RegisterSetBuffer.peek(FryskGui) at inua.eio.ByteBuffer.peekFully(FryskGui) at inua.eio.ByteBuffer.get(FryskGui) at frysk.proc.Register.get(FryskGui) at frysk.rt.StackCallbacks.accessReg(FryskGui) at lib.unwind.StackTraceCreator.unwind_setup(FryskGui) at lib.unwind.StackTraceCreator.createStackTrace(FryskGui) at frysk.rt.StackFactory.createStackFrame(FryskGui) at frysk.rt.StackFactory.createStackFrame(FryskGui) at frysk.gui.monitor.actions.CaptureStackFrameAction.execute(FryskGui) at frysk.gui.monitor.actions.TaskActionPoint.runActions(FryskGui) at frysk.gui.monitor.observers.TaskCloneObserver.runActionsParent(FryskGui) at frysk.gui.monitor.observers.TaskCloneObserver.bottomHalfParent(FryskGui) at frysk.gui.monitor.observers.TaskCloneObserver$1.run(FryskGui) at org.gnu.glib.CustomEvents.runEvents(libgtkjava-2.8.so) Which is likely caused by either the process not being blocked properly, or some other inconsistency with the Task being unwound. -- Summary: ptrace complains about monitor stack tracing Product: frysk Version: unspecified Status: NEW Severity: normal Priority: P2 Component: general AssignedTo: frysk-bugzilla at sourceware dot org ReportedBy: mcvet at redhat dot com CC: swagiaal at redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=4260 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
reply other threads:[~2007-03-22 15:38 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=20070322153757.4260.mcvet@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).