From: Christo Crause <christo.crause@gmail.com>
To: Klaus <lts-rudolph@gmx.de>
Cc: Simon Marchi <simark@simark.ca>, gdb@sourceware.org
Subject: Re: apply patch to avr-gdb to be able to debug on assembler level
Date: Sat, 23 May 2020 10:31:30 +0200 [thread overview]
Message-ID: <CAGOmfbG8PyzB6DwyNHOgw9+f8WQ9C_fsynG=FczFyaw55wUqiQ@mail.gmail.com> (raw)
In-Reply-To: <7db084e7-4f4f-2bd0-7c45-b18896b54a05@gmx.de>
On Fri, May 22, 2020 at 9:11 PM Klaus <lts-rudolph@gmx.de> wrote:
>
> It only makes me wonder that all people simply apply the patches by them
> self and nobody is crying to get it in the next release :-)
>
Have been wondering about this myself since I encountered this bug and
patch probably around 3-4 years ago. To me it seemed relatively easy to
implement the fix (even though I'm not really a C programmer) and the issue
has been reported already (apparently in the correct manner), so I didn't
bother pushing for inclusion of the fix.
The other possibility is that people using official software such as Atmel
Studio or MPLab are indirectly using either different debuggers or
different debugging techniques (via the IDE) so completely avoid the issue.
I have followed AVRFreaks for quite a few years now and even there the
complaints about this bug is really few and far between. Perhaps avr-gdb
is simply not used that widely?
next prev parent reply other threads:[~2020-05-23 8:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 13:37 Klaus Rudolph
2020-05-22 16:39 ` Christo Crause
2020-05-22 17:25 ` Simon Marchi
2020-05-22 19:10 ` Christo Crause
2020-05-22 19:11 ` Klaus
2020-05-23 8:31 ` Christo Crause [this message]
2020-05-24 14:25 ` Simon Marchi
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='CAGOmfbG8PyzB6DwyNHOgw9+f8WQ9C_fsynG=FczFyaw55wUqiQ@mail.gmail.com' \
--to=christo.crause@gmail.com \
--cc=gdb@sourceware.org \
--cc=lts-rudolph@gmx.de \
--cc=simark@simark.ca \
/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).