public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Petr Sumbera <petr.sumbera@oracle.com>, gdb@sourceware.org
Subject: Re: Solaris - procfs: couldn't find pid 32748 (kernel thread 21) in procinfo list
Date: Mon, 8 Jun 2020 14:47:22 +0100	[thread overview]
Message-ID: <fa28bcd8-b8c1-a8e1-8c9c-17fe86ba796c@redhat.com> (raw)
In-Reply-To: <98fb3303-e318-053a-6c20-8c809f9eb654@oracle.com>

On 6/8/20 10:51 AM, Petr Sumbera via Gdb wrote:
> On 03.06.2020 15:09, Petr Sumbera via Gdb wrote:
>> This works for few test cases. And I actually started gdb tests to see if it makes any regression (but it might take some time to run it though).
> 
> GDB tests on Solaris doesn't seem to deterministic. So I cannot confirm for 100% that the patch doesn't cause any regression. Though it rather seems it's not. See attached diff output between runs without and with the patch.
> 
> Can we get the patch to upstream now?

Please can send the version that you tested.  You mentioned
before that I had applied the fix to the wrong place.

Pedro Alves


      reply	other threads:[~2020-06-08 13:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-28 15:29 Petr Sumbera
2020-05-28 16:01 ` Rainer Orth
2020-06-01 12:47   ` Petr Sumbera
2020-06-01 11:39 ` Petr Sumbera
2020-06-01 19:12   ` Pedro Alves
2020-06-02  7:32     ` Petr Sumbera
2020-06-02 14:53       ` Pedro Alves
2020-06-02 16:30         ` Petr Sumbera
2020-06-02 17:14           ` Pedro Alves
2020-06-03 13:09             ` Petr Sumbera
2020-06-08  9:51               ` Petr Sumbera
2020-06-08 13:47                 ` Pedro Alves [this message]

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=fa28bcd8-b8c1-a8e1-8c9c-17fe86ba796c@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=petr.sumbera@oracle.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).