Summary: | ld.so immediately crashes after f5f7144dfcbf2a11fd2c17316c213928307c1db3 on hppa2.0-unknown-linux-gnu | ||
---|---|---|---|
Product: | glibc | Reporter: | Sam James <sam> |
Component: | dynamic-link | Assignee: | Not yet assigned to anyone <unassigned> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | drepper.fsp, nszabolcs |
Priority: | P2 | ||
Version: | 2.36 | ||
Target Milestone: | --- | ||
See Also: | https://sourceware.org/bugzilla/show_bug.cgi?id=23293 | ||
Host: | hppa2.0-unknown-linux-gnu | Target: | hppa2.0-unknown-linux-gnu |
Build: | hppa2.0-unknown-linux-gnu | Last reconfirmed: |
Description
Sam James
2022-06-10 00:07:26 UTC
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. To be clear, this is from using the 2.35 branch. Last good commit on release/2.35: a8e9b5b8079d18116ca69c9797e77804ecf2ee7e Last bad commit on release/2.35: d7d1eebd4d5806be55ffacbf18917ad68d4ae7fd Then bisected to release/2.35: f5f7144dfcbf2a11fd2c17316c213928307c1db3. |