public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/30062] glibc 2.36 loader has intermittent segfault error on ppc64le
Date: Wed, 01 Feb 2023 16:40:59 +0000	[thread overview]
Message-ID: <bug-30062-131-T7mWxMJ50x@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30062-131@http.sourceware.org/bugzilla/>

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

--- Comment #4 from Carlos O'Donell <carlos at redhat dot com> ---
I don't see anything obviously bad in the valgrind logs.

This may be a race condition in the DSOs you load and the data that they
access, or in the threads they create, and later join.

There isn't any conclusive proof here that we have a dyanmic loader race.

Please update this when you have more information from debugging the
reproducer.

I asked in the github issue, and I'll ask here for the record, what hardware
are you using?

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

  parent reply	other threads:[~2023-02-01 16:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31  5:45 [Bug dynamic-link/30062] New: " Qi.Chen at windriver dot com
2023-01-31 20:56 ` [Bug dynamic-link/30062] " carlos at redhat dot com
2023-02-01  4:46 ` Qi.Chen at windriver dot com
2023-02-01  4:48 ` Qi.Chen at windriver dot com
2023-02-01 16:40 ` carlos at redhat dot com [this message]
2023-02-01 20:57 ` rwmacleod at gmail dot com
2023-02-02  2:18 ` Qi.Chen at windriver dot com
2023-02-02  2:49 ` carlos at redhat dot com
2023-02-02  2:53 ` Qi.Chen at windriver dot com
2023-02-02  4:11 ` carlos at redhat dot com
2024-01-28  8:32 ` sam at gentoo dot org

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-30062-131-T7mWxMJ50x@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).