public inbox for frysk-bugzilla@sourceware.org help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org> To: frysk-bugzilla@sourceware.org Subject: [Bug general/4761] New: Task Memory view without inserted breakpoints showing Date: Tue, 10 Jul 2007 09:57:00 -0000 [thread overview] Message-ID: <20070710095741.4761.mark@klomp.org> (raw) When the user inspects the memory of a Task it should not be seeing any temporarily inserted breakpoint instructions that the frysk-core might have inserted. The core should use some 'RawMemory' view, while the rest of frysk should use a sanitized Memory buffer view that shows memory as if the original instructions are present. Use case: User inserts a breakpoint with fhpd or frysk-gui, runs the program and stops at the location and then inspects the instructions found around the place just stopped. Even when the breakpoint isn't removed already the user should see the original instructions, not the inserted breakpionts (which might disrupt the actual instruction stream). -- Summary: Task Memory view without inserted breakpoints showing Product: frysk Version: unspecified Status: NEW Severity: normal Priority: P2 Component: general AssignedTo: frysk-bugzilla at sourceware dot org ReportedBy: mark at klomp dot org http://sourceware.org/bugzilla/show_bug.cgi?id=4761 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2007-07-10 9:57 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-07-10 9:57 mark at klomp dot org [this message] 2007-07-11 9:46 ` [Bug general/4761] " 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=20070710095741.4761.mark@klomp.org \ --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).