public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "mnl at mnl dot de" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/13519] [avr][Regression 7.1/7.2/7.3/7.4] disassemble command attempts to disassemble SRAM rather than program memory
Date: Thu, 21 May 2020 14:03:34 +0000 [thread overview]
Message-ID: <bug-13519-4717-RbkgtPesP7@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13519-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=13519
--- Comment #22 from Michael N. Lipp <mnl at mnl dot de> ---
(In reply to Mauro Quiroga from comment #21)
> Any news regarding this bug and patch? Years has passed and still nothing
> has changed.
> Also, after reviewing the bug list I found that there is relationship with
> other bugs that were filed before and after, like:
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=9511
> https://sourceware.org/bugzilla/show_bug.cgi?id=12105
> https://sourceware.org/bugzilla/show_bug.cgi?id=12299
> https://sourceware.org/bugzilla/show_bug.cgi?id=16606
>
> The effects reported in all of them are the same, being the main problem the
> way the memory address is interpreted and used.
Kind of incredible, isn't it, how much time the inclusion of a 4 line patch
would have saved...
To be honest, having worked my whole professional live with bug trackers, I've
never understood how this mail-a-patch workflow is supposed to work.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-05-21 14:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 12:44 [Bug gdb/13519] New: [avr] " j at uriah dot heep.sax.de
2011-12-19 13:37 ` [Bug gdb/13519] " j at uriah dot heep.sax.de
2011-12-19 14:55 ` [Bug gdb/13519] [avr][Regression 7.1/7.2/7.3/7.4] " eric.weddington at atmel dot com
2012-02-24 11:27 ` mnl at mnl dot de
2012-02-24 11:28 ` mnl at mnl dot de
2012-02-24 11:31 ` mnl at mnl dot de
2012-02-27 19:34 ` tromey at redhat dot com
2012-03-09 16:01 ` eric.weddington at atmel dot com
2014-05-25 21:32 ` dwt at pobox dot com
2014-05-29 15:12 ` palves at redhat dot com
2014-05-30 18:40 ` dwt at pobox dot com
2014-07-07 18:17 ` cristiano.dealti at eurotech dot com
2014-07-08 19:52 ` cristiano.dealti at eurotech dot com
2015-05-24 17:41 ` cristiano.dealti at eurotech dot com
2020-05-21 3:57 ` msquirogac at gmail dot com
2020-05-21 14:03 ` mnl at mnl dot de [this message]
2020-05-25 15:57 ` cvs-commit at gcc dot gnu.org
2020-05-25 15:59 ` simark at simark dot ca
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-13519-4717-RbkgtPesP7@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).