public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Florian Weimer <fweimer@redhat.com>, libc-alpha@sourceware.org
Cc: gdb@sourceware.org
Subject: Re: [PATCH] nptl: Export libthread_db-used symbols under GLIBC_PRIVATE
Date: Sun, 20 Jun 2021 08:38:07 -0400	[thread overview]
Message-ID: <4df1e03a-eead-82b2-289f-b6cb7ddc0159@polymtl.ca> (raw)
In-Reply-To: <877disuwfq.fsf@oldenburg.str.redhat.com>

On 2021-06-17 3:23 p.m., Florian Weimer via Gdb wrote:
> Kevin, this *almost* gives us the perfect debugging experience with your
> patched GDB in Fedora 35, according to my preliminary tests.  A build
> with the patch is running here:
> 
>   <https://koji.fedoraproject.org/koji/buildinfo?buildID=1773177>
> 
> However, it seems that GDB still needs pthread_create in the .symtab to
> trigger loading of libpthread_db.  A fully stripped libc.so.6 without
> .symtab does not trigger loading in my experiments.  (The other symbols
> we preserve for valgrind's sake and are immaterial to GDB.)  In other
> words,

Stupid question, but: since pthread_create is a function exposed by the
libc.so shared library, won't there still be an entry for it in .dynsym?
And if so, shouldn't GDB see it?

Simon

  reply	other threads:[~2021-06-20 12:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-17 19:23 Florian Weimer
2021-06-20 12:38 ` Simon Marchi [this message]
2021-06-27 22:25   ` Carlos O'Donell
2021-06-29 14:20     ` Simon Marchi
2021-06-29 14:24       ` Florian Weimer
2021-06-28  2:10 ` Carlos O'Donell
2021-06-28  8:34   ` Florian Weimer

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=4df1e03a-eead-82b2-289f-b6cb7ddc0159@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=fweimer@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=libc-alpha@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).