public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "alex_y_xu at yahoo dot ca" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/28453] ld.so segfaults when relocating x86 libstdc++.so compiled with -fno-plt
Date: Tue, 28 Dec 2021 17:32:05 +0000	[thread overview]
Message-ID: <bug-28453-131-JZn7EROocP@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28453-131@http.sourceware.org/bugzilla/>

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

--- Comment #15 from alex_y_xu at yahoo dot ca ---
(In reply to H.J. Lu from comment #14)
> (In reply to alex_y_xu from comment #13)
> > Although I have not tested it, the linked patch does not appear to resolve
> > this issue. While I think the patch is a good idea, this issue is not
> > actually about invoking ld.so directly on the library. All programs linked
> > against this library also segfault on execution.
> > 
> > $ docker run -it --rm fedora
> > [ ... ]
> > # dnf install g++ glibc-devel.i686 libstdc++-devel.i686
> > [ ... ]
> > # curl -o libstdc++.so.6
> > https://sourceware.org/bugzilla/attachment.cgi?id=13721
> > [ ... ]
> > # echo 'int main() {}' | g++ -m32 -x c++ -
> > # ./a.out; echo $?
> > 0
> > # LD_LIBRARY_PATH=. ./a.out; echo $?
> > Segmentation fault (core dumped)
> > 139
> 
> Try:
> 
> https://sourceware.org/pipermail/libc-alpha/2021-December/134004.html

I wasn't able to apply this to glibc 2.34 or glibc master. Are you sure it will
fix the issue of a.out crashing in the above example?

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

      parent reply	other threads:[~2021-12-28 17:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-15  0:45 [Bug dynamic-link/28453] New: " alex_y_xu at yahoo dot ca
2021-10-25  1:23 ` [Bug dynamic-link/28453] " sam at gentoo dot org
2021-11-17  8:43 ` fweimer at redhat dot com
2021-11-17 13:09 ` hjl.tools at gmail dot com
2021-11-17 13:31 ` alex_y_xu at yahoo dot ca
2021-11-17 14:10 ` hjl.tools at gmail dot com
2021-11-17 14:17 ` fweimer at redhat dot com
2021-11-17 14:39 ` alex_y_xu at yahoo dot ca
2021-11-17 14:58 ` hjl.tools at gmail dot com
2021-11-17 14:59 ` hjl.tools at gmail dot com
2021-11-17 16:05 ` hjl.tools at gmail dot com
2021-12-09 17:47 ` alex_y_xu at yahoo dot ca
2021-12-09 17:51 ` alex_y_xu at yahoo dot ca
2021-12-10  2:32 ` hjl.tools at gmail dot com
2021-12-10 16:02 ` alex_y_xu at yahoo dot ca
2021-12-10 19:55 ` hjl.tools at gmail dot com
2021-12-28 17:32 ` alex_y_xu at yahoo dot ca [this message]

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-28453-131-JZn7EROocP@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).