public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "mliska at suse dot cz" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/27580] gcore: stream libthread_db information
Date: Tue, 17 Jan 2023 13:57:31 +0000	[thread overview]
Message-ID: <bug-27580-4717-tjGuKff76j@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27580-4717@http.sourceware.org/bugzilla/>

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

--- Comment #3 from Martin Liska <mliska at suse dot cz> ---
The message will be displayed if you debug a core file from a machine that has
e.g. ancient version of glibc:

gdb/linux-thread-db.c:

/* Predicate which tests whether objfile OBJ refers to the library
   containing pthread related symbols.  Historically, this library has
   been named in such a way that looking for "libpthread" in the name
   was sufficient to identify it.  As of glibc-2.34, the C library
   (libc) contains the thread library symbols.  Therefore we check
   that the name matches a possible thread library, but we also check
   that it contains at least one of the symbols (pthread_create) that
   we'd expect to find in the thread library.  */

static bool
libpthread_objfile_p (objfile *obj)
{
  return (libpthread_name_p (objfile_name (obj))
          && lookup_minimal_symbol ("pthread_create",
                                    NULL,
                                    obj).minsym != NULL);
}

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2023-01-17 13:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-15 13:44 [Bug gdb/27580] New: " mliska at suse dot cz
2021-03-15 13:45 ` [Bug gdb/27580] " mliska at suse dot cz
2022-08-08  8:56 ` mliska at suse dot cz
2023-01-13  8:42 ` mliska at suse dot cz
2023-01-16 22:48 ` amerey at redhat dot com
2023-01-17 13:57 ` mliska at suse dot cz [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=bug-27580-4717-tjGuKff76j@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).