From: Simon Marchi <simark@simark.ca>
To: Christo Crause <christo.crause@gmail.com>,
Klaus Rudolph <lts-rudolph@gmx.de>
Cc: gdb@sourceware.org
Subject: Re: apply patch to avr-gdb to be able to debug on assembler level
Date: Fri, 22 May 2020 13:25:09 -0400 [thread overview]
Message-ID: <234fc85f-1844-9dc7-277a-aaaa61c320e5@simark.ca> (raw)
In-Reply-To: <CAGOmfbFQYZMTyQJtR4b9wbLJSA_g9Fa3853FL4xMjZ17bYXuag@mail.gmail.com>
On 2020-05-22 12:39 p.m., Christo Crause via Gdb wrote:
> On Fri, May 22, 2020 at 4:06 PM Klaus Rudolph <lts-rudolph@gmx.de> wrote:
>
>> Hi,
>>
>> I today run into a well known problem with avr-gdb.
>> There is already a patch provided within the bug report.
>>
>>
>> https://sourceware.org/bugzilla/show_bug.cgi?id=13519
>>
>
> Indeed, the curious case of the apparently straight-forward fix that hasn't
> been applied. Is there actually a maintainer for the AVR port?
>
> On the flip side this bug forced me to figure out how to patch and build
> avr-gdb myself.
>
Hi,
I saw the activity on the bug report yesterday. It's unfortunate, but if you
want something to progress, you just need to ping it now and then, otherwise
it just gets buried in the volume of emails and patches. If the patch was sent
in 2016 and hasn't seen any activity since, there's no real change that some
GDB maintainer will pick it up, review it, test it and merge it out of nowhere
(unless they need it themselves).
And indeed, there's isn't a maintainer dedicated to AVR in GDB, so that doesn't
help.
I would like to see this merged, so I'm working on getting at least a bit of the
GDB testsuite running against simavr. If that works well enough, at least we'll
get some confidence that this change doesn't break some other use case.
Simon
next prev parent reply other threads:[~2020-05-22 17:25 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 [this message]
2020-05-22 19:10 ` Christo Crause
2020-05-22 19:11 ` Klaus
2020-05-23 8:31 ` Christo Crause
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=234fc85f-1844-9dc7-277a-aaaa61c320e5@simark.ca \
--to=simark@simark.ca \
--cc=christo.crause@gmail.com \
--cc=gdb@sourceware.org \
--cc=lts-rudolph@gmx.de \
/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).