public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "nav at bloom dot oscillate.io" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/12105] [AVR] disassemble START,END dumps data memory (SRAM)
Date: Tue, 28 Sep 2021 19:18:42 +0000	[thread overview]
Message-ID: <bug-12105-4717-3EjN9iAtVS@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12105-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=12105

Nav <nav at bloom dot oscillate.io> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nav at bloom dot oscillate.io

--- Comment #1 from Nav <nav at bloom dot oscillate.io> ---
Created attachment 13683
  --> https://sourceware.org/bugzilla/attachment.cgi?id=13683&action=edit
screenshot of failed attempt to reproduce bug

This is a result of 13519
(https://sourceware.org/bugzilla/show_bug.cgi?id=13519), which has since been
resolved. I cannot replicate this issue on GDB 11.0.50 (see attached
screenshot). GDB no longer applies the SRAM offset when reading program memory
for disassemble operations.

I believe this has been fixed since version 10.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2021-09-28 19:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-09 21:16 [Bug tdep/12105] New: AVR: " news at schildmann dot info
2010-10-09 21:32 ` [Bug tdep/12105] [AVR] " news at schildmann dot info
2021-09-28 19:18 ` nav at bloom dot oscillate.io [this message]

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=bug-12105-4717-3EjN9iAtVS@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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: link
Be 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).