public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Klaus <lts-rudolph@gmx.de>
To: Simon Marchi <simark@simark.ca>,
	Christo Crause <christo.crause@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: apply patch to avr-gdb to be able to debug on assembler level
Date: Fri, 22 May 2020 21:11:53 +0200	[thread overview]
Message-ID: <7db084e7-4f4f-2bd0-7c45-b18896b54a05@gmx.de> (raw)
In-Reply-To: <234fc85f-1844-9dc7-277a-aaaa61c320e5@simark.ca>

Am 22.05.20 um 19:25 schrieb Simon Marchi:

>
> 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

Thats why I wrote my mail. I also see that we had some comment on that
patch yesterday. It is simply by accident that I run into the very old
bug today and find that old bug entry. I found it, because I applied
these patches for years again and again to every new gdb version and had
a notice on my patching script for that bug.

> 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.
>

As always in open source, if there is nobody actively self working on
something, nothing will change. No problem!


> 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.
>

I believe we have a bit confidence on the older patch which was working
for years very well. As I applied that patch today against 9.1 release
and get everything working, it feels ok to apply it to the mainline.
Even if it will break something, we will have some user reports for that
and maybe the next patch. But simply doing nothing because maybe
something can be broken did also not help. As mentioned, the patch is
local to avr. It can be tested with simulavr as with real jtag
interface. Testability is not a problem in that case.

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 :-)

Maybe avr is dead as all the arm stuff has taken over the small 8 bit
systems. And for me it is only a small project which I want to run
today... but keeps me searching for old bugs :-)

If I can support something, maybe for testing, feel free to ask.


  Klaus



  parent reply	other threads:[~2020-05-22 19:11 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 [this message]
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=7db084e7-4f4f-2bd0-7c45-b18896b54a05@gmx.de \
    --to=lts-rudolph@gmx.de \
    --cc=christo.crause@gmail.com \
    --cc=gdb@sourceware.org \
    --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).