public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Szabolcs Nagy <szabolcs.nagy@arm.com>
Cc: Pedro Alves <palves@redhat.com>,
	 gdb-patches@sourceware.org,
	 Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH v3] nptl_db: Support different libpthread/ld.so load orders (bug 27744)
Date: Thu, 22 Apr 2021 13:55:54 +0200	[thread overview]
Message-ID: <87pmymildh.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20210422094808.GJ9028@arm.com> (Szabolcs Nagy's message of "Thu,  22 Apr 2021 10:48:09 +0100")

* Szabolcs Nagy:

> The 04/22/2021 10:05, Szabolcs Nagy via Gdb-patches wrote:
>> The 04/22/2021 10:33, Florian Weimer wrote:
>> > * Szabolcs Nagy:
>> > > on the aarch64 buildbot i see
>> > >
>> > > FAIL: nptl/tst-pthread-gdb-attach
>> > >
>> > > $ cat nptl/tst-pthread-gdb-attach.out
>> > > +set debug libthread-db 1
>> > > +add-symbol-file /work/glibc-aarch64-linux/build/build/nptl/tst-pthread-gdb-attach
>> > > add symbol table from file "/work/glibc-aarch64-linux/build/build/nptl/tst-pthread-gdb-attach"
>> > > +set auto-load safe-path /work/glibc-aarch64-linux/build/build/nptl_db
>> > > +set libthread-db-search-path /work/glibc-aarch64-linux/build/build/nptl_db
>> > > +attach 461328
>> > > [New LWP 461329]
>> > > Trying host libthread_db library: /work/glibc-aarch64-linux/build/build/nptl_db/libthread_db.so.1.
>> > > td_ta_new failed: application not linked with libthread
>> > > thread_db_load_search returning 0
>> > 
>> > Unfortunately I cannot reproduce this with binutils 2.30, GDB 8.2 and
>> > GCC 8.4.1.  Has your environment newer or older versions?
>> 
>> ubuntu flavour of
>> 
>> gcc 8.2.0
>> binutils 2.31.1
>> gdb 8.2
>> 
>> happens on armhf and aarch64 too.
>
> happens with gcc-10.2.0, gdb-9.2, binutils-2.34 too
> (still ubuntu)

Still no luck with binutils 2.35.1, a GCC 11 snapshot, and GDB 10.1.

Do you run this test as a regular user?  Could it be caused by YAMA
ptrace policies?

Thanks,
Florian


  reply	other threads:[~2021-04-22 11:55 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
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 [this message]
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=87pmymildh.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=libc-alpha@sourceware.org \
    --cc=palves@redhat.com \
    --cc=szabolcs.nagy@arm.com \
    /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).