From: "H.J. Lu" <hjl.tools@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>,
Simon Marchi <simon.marchi@polymtl.ca>,
Pedro Alves <palves@redhat.com>,
Kevin Buettner <kevinb@redhat.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH v3] nptl_db: Support different libpthread/ld.so load orders (bug 27744)
Date: Wed, 21 Apr 2021 15:35:27 -0700 [thread overview]
Message-ID: <CAMe9rOo2z7XAqQ54G75JC-Nk_PuqpetREBpchn1cZSG0szxMrA@mail.gmail.com> (raw)
In-Reply-To: <87czunoo5m.fsf@oldenburg.str.redhat.com>
On Wed, Apr 21, 2021 at 6:04 AM Florian Weimer via Libc-alpha
<libc-alpha@sourceware.org> wrote:
>
> * Florian Weimer via Libc-alpha:
>
> > libthread_db is loaded once GDB encounters libpthread, and at this
> > point, ld.so may not have been processed by GDB yet. As a result,
> > _rtld_global cannot be accessed by regular means from libthread_db.
> > To make this work until GDB can be fixed, acess _rtld_global through
> > a pointer stored in libpthread.
> >
> > The new test does not reproduce bug 27744 with
> > --disable-hardcoded-path-in-tests, but is still a valid smoke test.
> > With --enable-hardcoded-path-in-tests, it is necessary to avoid
> > add-symbol-file because this can tickle a GDB bug.
> >
> > Fixes commit 1daccf403b1bd86370eb94edca794dc106d02039 ("nptl: Move
> > stack list variables into _rtld_global").
> >
> > ---
> > v3: Mark test as UNSUPPORTED if launching gdb fails with ENOENT.
> > This is the version I'd like to commit soon.
>
> I've pushed this version given that Pedro acknowledged v2.
>
I got
FAIL: nptl/tst-pthread-gdb-attach
FAIL: nptl/tst-pthread-gdb-attach-static
when testing i686 build on Fedora 33:
[New LWP 1329590]
Trying host libthread_db library:
/export/build/gnu/tools-build/glibc-32bit-cet-gitlab/build-i686-linux/nptl_db/libthread_db.so.1.
dlopen failed: /export/build/gnu/tools-build/glibc-32bit-cet-gitlab/build-i686-linux/nptl_db/libthread_db.so.1:
wrong ELF class: ELFCLASS32.
thread_db_load_search returning 0
Is it possible to skip this when gdb and libthread_db.so.1 have different
ELC classes?
--
H.J.
next prev parent reply other threads:[~2021-04-21 22:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 10:40 Florian Weimer
2021-04-21 11:47 ` Florian Weimer
2021-04-21 22:35 ` H.J. Lu [this message]
2021-04-22 9:29 ` Florian Weimer
2021-04-22 7:28 ` Szabolcs Nagy
2021-04-22 8:33 ` Florian Weimer
2021-04-22 9:05 ` Szabolcs Nagy
2021-04-22 9:48 ` Szabolcs Nagy
2021-04-22 11:55 ` Florian Weimer
2021-04-22 12:44 ` Szabolcs Nagy
2021-04-22 14:20 ` Szabolcs Nagy
2021-04-22 14:25 ` Florian Weimer
2021-04-22 15:30 ` Szabolcs Nagy
2021-04-22 15:39 ` Florian Weimer
2021-04-22 17:22 ` H.J. Lu
2021-04-22 17:56 ` Florian Weimer
2021-04-22 18:27 ` H.J. Lu
2021-04-22 14:34 ` H.J. Lu
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=CAMe9rOo2z7XAqQ54G75JC-Nk_PuqpetREBpchn1cZSG0szxMrA@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=fweimer@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=palves@redhat.com \
--cc=simon.marchi@polymtl.ca \
/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).