public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Andrew Burgess <andrew.burgess@embecosm.com>,
	GDB Patches <gdb-patches@sourceware.org>,
	Philippe Waroquiers <philippe.waroquiers@skynet.be>,
	Pedro Alves <palves@redhat.com>
Subject: Re: [PATCH] Fix printf of a convenience variable holding an inferior address
Date: Mon, 09 Mar 2020 18:56:56 -0400	[thread overview]
Message-ID: <877dztgmrr.fsf@redhat.com> (raw)
In-Reply-To: <20200307115849.GA20426@adacore.com> (Joel Brobecker's message of "Sat, 7 Mar 2020 12:58:49 +0100")

On Saturday, March 07 2020, Joel Brobecker wrote:

>> Yeah, this is a regression.  GDB 8.3 worked fine.
>
> OK. Thanks for confirming, Sergio.
>
>> > In terms of putting it in 9.2, I think we could do it; the patch
>> > does look safe to me.
>> 
>> Cool.  So, is the process the same (now that we're using a different
>> versioning scheme)?  Do I just open a bug again 9.1 and push the
>> backported patch to the branch?
>
> Correct :). If you don't mind, it might be useful to amend the
> ChangeLog entry in master to include the PR number.

Alright, I just pushed a new commit to the gdb-9-branch:

https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=141e490226a99e0359393ddaca5628c68de036dc

The bug is:

https://sourceware.org/bugzilla/show_bug.cgi?id=25650

I didn't set the Target Milestone there because I didn't see a "9.2" (or
"9.1.1"?) option.

Let me know if there's anything else I need to do :-).

> Thanks Sergio!

Thank you!

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


  reply	other threads:[~2020-03-09 22:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-10 21:16 [RFA] Ensure GDB printf command can print convenience var strings without a target Philippe Waroquiers
2019-06-11  2:29 ` Eli Zaretskii
2019-07-05 20:01 ` PING " Philippe Waroquiers
2019-07-08 18:13 ` Pedro Alves
2019-07-08 22:41   ` Philippe Waroquiers
2019-07-09  4:36     ` New FAIL on gdb.base/printcmds.exp (was: Re: [RFA] Ensure GDB printf command can print convenience var strings without a target.) Sergio Durigan Junior
2020-03-02  2:46 ` [PATCH] Fix printf of a convenience variable holding an inferior address Sergio Durigan Junior
2020-03-03 13:39   ` Andrew Burgess
2020-03-03 16:29     ` Sergio Durigan Junior
2020-03-03 16:49       ` Sergio Durigan Junior
2020-03-04 10:53         ` Joel Brobecker
     [not found]           ` <8736al5d8s.fsf@redhat.com>
2020-03-07 11:58             ` Joel Brobecker
2020-03-09 22:56               ` Sergio Durigan Junior [this message]
2020-03-10 22:37                 ` Joel Brobecker
2020-03-10 22:57                   ` Sergio Durigan Junior
2020-03-10 23:13                     ` Andreas Schwab
2020-03-10 23:38                       ` Sergio Durigan Junior
2020-03-11 16:34                   ` Sergio Durigan Junior

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=877dztgmrr.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=andrew.burgess@embecosm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=philippe.waroquiers@skynet.be \
    /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).