public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>,
	Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB 10.1 release: branching early July?
Date: Thu, 18 Jun 2020 20:57:18 +0100	[thread overview]
Message-ID: <1a0022cd-af10-6a19-8b34-c3d2e8d5e23c@redhat.com> (raw)
In-Reply-To: <20200615225350.GG7711@adacore.com>

Hi Joel,

On 6/15/20 11:53 PM, Joel Brobecker wrote:
>>>   * [unassigned]
>>>     <PR gdb/25412> thread_info with duplicate ptid added to inferior thread list
>>>     https://sourceware.org/bugzilla/show_bug.cgi?id=25412
>>>
>>>     Reported by Simon, who started investigating a bit.
>>>     Simon says the issue appeared after the "multi-target" patch
>>>     series went in (5b6d1e4fa by Pedro).
>>>
>>>     Simon - is that still an issue?
>>
>> Yes, Pedro has a patch series to address it here:
>>
>>   https://sourceware.org/pipermail/gdb-patches/2020-April/167578.html
>>
>> We need to get back to it and get it merged.
> 
> Thanks for the update and the URL, Simon. This is super helpful
> for me to keep track of progress.
> 

I'm addressing the review comments of that series today.

Thanks,
Pedro Alves


  reply	other threads:[~2020-06-18 19:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-14  1:56 Joel Brobecker
2020-06-14  2:04 ` Simon Marchi
2020-06-15 22:53   ` Joel Brobecker
2020-06-18 19:57     ` Pedro Alves [this message]
2020-06-14 15:14 ` Rainer Orth
2020-06-15 23:09   ` Joel Brobecker
2020-06-16 13:49     ` Rainer Orth
2020-06-16 18:13       ` Joel Brobecker
2020-06-14 15:32 ` Hannes Domani
2020-06-15 23:17   ` Joel Brobecker
2020-06-16 20:28     ` Tom Tromey
2020-06-14 16:53 ` Philippe Waroquiers
2020-06-14 16:57   ` Philippe Waroquiers
2020-06-16  0:13     ` Joel Brobecker
2020-06-26 11:36 ` Luis Machado
2020-06-26 16:26   ` Joel Brobecker
2020-06-26 19:27     ` Luis Machado

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=1a0022cd-af10-6a19-8b34-c3d2e8d5e23c@redhat.com \
    --to=palves@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.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).