public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Luis Machado <luis.machado@arm.com>,
	Joel Brobecker <brobecker@adacore.com>,
	Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>,
	tom@tromey.com
Cc: gdb-patches@sourceware.org
Subject: Re: GDB 13 release -- 2023-01-21 Update
Date: Fri, 27 Jan 2023 12:17:49 -0500	[thread overview]
Message-ID: <fd12535c-97a5-db8b-7228-1b3ab08b697c@polymtl.ca> (raw)
In-Reply-To: <47dff98e-b714-2d72-bc3b-c14c4e0313d0@arm.com>

>>    - With that said, the patch appears to simply add a cache,
>>      so the logic of it all doesn't appear to be extremely
>>      complicated. So I would rate the risk to be low.
> 
> That's what it seems to me.
> 
> I think another round of testing would be a good step to make sure there are no hidden bugs.
My understanding is that the problem was making debugging borderline
impossible.  Or at least, really, really unpleasant.  So I think it
qualifies as a bug fix, and that the benefit is worth the risk.

Simon



  reply	other threads:[~2023-01-27 17:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-21  6:08 Joel Brobecker
2023-01-25 20:18 ` Torbjorn SVENSSON
2023-01-27  6:30   ` Joel Brobecker
2023-01-27  6:38     ` Luis Machado
2023-01-27 17:17       ` Simon Marchi [this message]
2023-01-28  8:39         ` Luis Machado
2023-01-29 11:52           ` Joel Brobecker
2023-01-30 11:23             ` Luis Machado
2023-01-31  7:03               ` Joel Brobecker
2023-01-31 13:57                 ` Luis Machado
2023-01-31 14:33                   ` Luis Machado
2023-02-02  3:44                   ` Joel Brobecker

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=fd12535c-97a5-db8b-7228-1b3ab08b697c@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=luis.machado@arm.com \
    --cc=tom@tromey.com \
    --cc=torbjorn.svensson@foss.st.com \
    /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).