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/4648] New: Trying to read from start_thread () frame gives ptrace errors Date: Fri, 15 Jun 2007 12:33:00 -0000 [thread overview] Message-ID: <20070615123336.4648.mcvet@redhat.com> (raw) I will attach a test program in a minute to demonstrate - on x86_64, loading this program into the source window, and then attempting to read information from the start_thread frame (which shows up as the second [unknown] frame in the second thread) reliably prints out ptrace errors each time the frame is clicked, resulting in no information in the window. ptrace: Input/output error (pt 0x2, pid 11167, addr 0x555555998540, data 0x0) at frysk.sys.Ptrace$AddressSpace.peek(FryskGui) at frysk.proc.ptrace.AddressSpaceByteBuffer$PeekRequest.execute(FryskGui) at frysk.event.Request$Handler.execute(FryskGui) at frysk.event.EventLoop.runEventLoop(FryskGui) at frysk.event.EventLoop.run(FryskGui) at frysk.gui.Gui$4.run(FryskGui) at java.lang.Thread.run(libgcj.so.7rh) -- Summary: Trying to read from start_thread () frame gives ptrace errors 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 OtherBugsDependingO 1633 nThis: http://sourceware.org/bugzilla/show_bug.cgi?id=4648 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2007-06-15 12:33 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-06-15 12:33 mcvet at redhat dot com [this message] 2007-06-15 12:34 ` [Bug general/4648] " mcvet at redhat dot com 2007-06-15 13:47 ` mcvet at redhat dot com 2007-08-01 19:48 ` 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=20070615123336.4648.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).