public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sam at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/29237] ld.so immediately crashes after f5f7144dfcbf2a11fd2c17316c213928307c1db3 on hppa2.0-unknown-linux-gnu
Date: Fri, 10 Jun 2022 00:07:43 +0000	[thread overview]
Message-ID: <bug-29237-131-B3TthaKrMB@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29237-131@http.sourceware.org/bugzilla/>

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

--- Comment #1 from Sam James <sam at gentoo dot org> ---
I can reproduce if I run the final command manually (LC_ALL=C gdb --args
./ld.so.1 --library-path . /usr/bin/cal, in
/var/tmp/portage/sys-libs/glibc-2.35-r7/image/lib) using the just-built glibc.

```
Program received signal SIGSEGV, Segmentation fault.
0xf8f0405c in ?? () from ./libc.so.6
(gdb) bt
#0  0xf8f0405c in ?? () from ./libc.so.6
#1  0xf8f044cc in ?? () from ./libc.so.6
#2  0xf8f04588 in getopt_long () from ./libc.so.6
#3  0xf9690084 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
```

Not very helpful.

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

  reply	other threads:[~2022-06-10  0:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10  0:07 [Bug libc/29237] New: " sam at gentoo dot org
2022-06-10  0:07 ` sam at gentoo dot org [this message]
2022-06-10  0:12 ` [Bug dynamic-link/29237] " sam at gentoo dot org
2022-06-10  0:15 ` sam at gentoo dot org
2022-06-10  2:52 ` 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-29237-131-B3TthaKrMB@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).