From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Petr Sumbera via Gdb <gdb@sourceware.org>
Subject: Re: Solaris - procfs: couldn't find pid 32748 (kernel thread 21) in procinfo list
Date: Thu, 28 May 2020 18:01:24 +0200 [thread overview]
Message-ID: <ydd8shcvyjv.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <5ab0b8b1-6072-6717-1ae0-ba06339254b8@oracle.com> (Petr Sumbera via Gdb's message of "Thu, 28 May 2020 17:29:40 +0200")
Hi Petr,
> I'm running into the issue below. Any suggestion how to this?
>
> # DISPLAY=:1 gdb /opt/firefox/bin/firefox
> GNU gdb (GDB) 9.2
> Copyright (C) 2020 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> Type "show copying" and "show warranty" for details.
> This GDB was configured as "sparc-sun-solaris2.11".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>.
> Find the GDB manual and other documentation resources online at:
> <http://www.gnu.org/software/gdb/documentation/>.
>
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from /opt/firefox/bin/firefox...
> (gdb) run -P
> Starting program: /opt/firefox/bin/firefox -P
> [Thread debugging using libthread_db enabled]
> [New Thread 1 (LWP 1)]
> [New LWP 2 ]
[...]
> [New LWP 26 ]
> [LWP 20 exited]
> [New LWP 20 ]
> [LWP 21 exited]
> [New LWP 21 ]
> procfs: couldn't find pid 32748 (kernel thread 21) in procinfo list.
> procfs: couldn't find pid 32748 (kernel thread 21) in procinfo list.
> (gdb)
>
> ---
>
> Is this Solaris GDB issue? Any suggestion where to look in GDB code?
I'm seeing this relatively often when running the gdb testsuite (which
makes it unsuitable to run make check on the Solaris gdb buildbots).
I haven't yet gotten around to investigate closely, but the first places
to check are procfs.c (the process layer, via /proc) and sol-thread.c
(the thread layer, via libc_db).
There's lots of old cruft in there from pre-Solaris 9 times with its NxM
thread model, which both breaks a considerable number of test cases and
makes the code harder to follow due to the added complexity/generality
we don't need any longer.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2020-05-28 16:01 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 [this message]
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
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=ydd8shcvyjv.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=gdb@sourceware.org \
/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