public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v3] nptl: Export libthread_db-used symbols under GLIBC_PRIVATE
Date: Tue, 29 Jun 2021 10:25:39 +0100	[thread overview]
Message-ID: <20210629092539.GA14854@arm.com> (raw)
In-Reply-To: <87o8bpox4u.fsf@oldenburg.str.redhat.com>

The 06/29/2021 11:09, Florian Weimer via Libc-alpha wrote:
> * Szabolcs Nagy:
> 
> > The 06/28/2021 08:59, Carlos O'Donell via Libc-alpha wrote:
> >> On 6/28/21 8:41 AM, Florian Weimer wrote:
> >> > This allows distributions to strip debugging information from
> >> > libc.so.6 without impacting the debugging experience.
> >> 
> >> This looks good, no redundant checks. The only *MAIN* symbol
> >> left in structs.def is from ld.so and we skip checking it
> >> (because the test framework only processes libc.so's symbols).
> >> 
> >> Reviewed-by: Carlos O'Donell <carlos@redhat.com>
> >
> > after the previous two nptl_db commits i see
> >
> > FAIL: nptl_db/db-symbols
> >
> > i thought this third patch would fix it, but it didn't:
> >
> > $ head nptl_db/db-symbols.out
> > _thread_db_pthread_eventbuf_eventmask_event_bits@@GLIBC_PRIVATE ***MISSING***
> > _thread_db_pthread_start_routine@@GLIBC_PRIVATE ***MISSING***
> > _thread_db_sizeof_list_t@@GLIBC_PRIVATE ***MISSING***
> > _thread_db_pthread_schedparam_sched_priority@@GLIBC_PRIVATE ***MISSING***
> > _thread_db_td_eventbuf_t_eventdata@@GLIBC_PRIVATE ***MISSING***
> > _thread_db_list_t_prev@@GLIBC_PRIVATE ***MISSING***
> > _thread_db_sizeof_dtv_slotinfo@@GLIBC_PRIVATE ***MISSING***
> > _thread_db_pthread_cancelhandling@@GLIBC_PRIVATE ***MISSING***
> > _thread_db___pthread_keys@@GLIBC_PRIVATE ***MISSING***
> > _thread_db_rtld_global__dl_tls_dtv_slotinfo_list@@GLIBC_PRIVATE ***MISSING***
> >
> > is this expected?
> 
> It is not expected.  The test runs even when cross-compiling, and I
> don't see this failure in a default build-many-glibcs.py run.
> 
> Are these symbols present as dynamic symbols in your build of libc.so.6?
> 
> I suspect your readelf has different output not expected by the script.
> Apparently older versions do not print symbol versioning information
> with -D -s. 8-( I guess we should parse ELF directly, rather than
> readelf output, because it is easier to maintain.
> 
> As a stop-gap measure, we should probably switch to objdump -T.

yes i can confirm that my readelf does not print symbol versions
with -D -s.

GNU readelf (GNU Binutils for Ubuntu) 2.31.1

i can try to update it if it's considered too old.

  reply	other threads:[~2021-06-29  9:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-28 12:41 Florian Weimer
2021-06-28 12:59 ` Carlos O'Donell
2021-06-29  8:21   ` Szabolcs Nagy
2021-06-29  9:09     ` Florian Weimer
2021-06-29  9:25       ` Szabolcs Nagy [this message]
2021-06-29  9:37         ` 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=20210629092539.GA14854@arm.com \
    --to=szabolcs.nagy@arm.com \
    --cc=fweimer@redhat.com \
    --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).