Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15456] No more login on Raspberry Pi 3 since 2023.02
Date: Sun, 19 Mar 2023 20:36:02 +0000	[thread overview]
Message-ID: <bug-15456-163-o07RnUxNPi@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15456-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=15456

--- Comment #3 from Peter Seiderer <ps.report@gmx.net> ---
Tested on raspberrypi_4, bash crashes with:

    $ ./host/bin/arm-buildroot-linux-gnueabihf-gdb build/bash-5.2.15/bash
core.199
    Core was generated by `bash'.
    Program terminated with signal SIGSEGV, Segmentation fault.
    #0  0xb6d74b5c in ?? ()
    (gdb) set sysroot ./staging
    Reading symbols from ./staging/lib/libreadline.so.8...
    Reading symbols from ./staging/lib/libhistory.so.8...
    Reading symbols from ./staging/lib/libncurses.so.6...
    Reading symbols from ./staging/lib/libc.so.6...
    Reading symbols from ./staging/lib/ld-linux-armhf.so.3...
    (gdb) where
    #0  0xb6d74b5c in kill () at ../sysdeps/unix/syscall-template.S:120
    #1  0x004d4f0c in kill_shell (sig=sig@entry=11) at sig.c:643
    #2  0x004d5110 in termsig_handler (sig=11) at sig.c:624
    #3  termsig_handler (sig=11) at sig.c:575
    #4  0x004d5248 in termsig_sighandler (sig=<optimized out>) at sig.c:558
    #5  <signal handler called>
    #6  strlen () at ../sysdeps/arm/strlen.S:32
    #7  0xb6f2fb20 in _rl_init_locale () at ../nls.c:150
    #8  0xb6f2fba0 in _rl_init_eightbit () at ../nls.c:227
    #9  0xb6f10f54 in readline_initialize_everything () at ../readline.c:1292
    #10 rl_initialize () at ../readline.c:1183
    #11 0x004e439c in initialize_readline () at bashline.c:522
    #12 0x0048e63c in yy_readline_get ()
        at /usr/local/src/chet/src/bash/src/parse.y:1514
    #13 0x00491190 in shell_getc (
        remove_quoted_newline=remove_quoted_newline@entry=1)
        at /usr/local/src/chet/src/bash/src/parse.y:2393
    #14 0x00493410 in read_token (command=0)
        at /usr/local/src/chet/src/bash/src/parse.y:3404
    #15 read_token (command=0) at /usr/local/src/chet/src/bash/src/parse.y:3355
    #16 0x00496a64 in yylex () at /usr/local/src/chet/src/bash/src/parse.y:2892
    #17 yyparse () at y.tab.c:1854
    #18 0x0048da38 in parse_command () at eval.c:348
    #19 0x0048db88 in read_command () at eval.c:392
    #20 0x0048dd10 in reader_loop () at eval.c:139
    #21 0x0048c7e8 in main (argc=5489868, argv=0x0, env=<optimized out>)
        at shell.c:833

But e.g. 'LANG=C bash' runs fine...

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2023-03-19 20:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-19  9:28 [Buildroot] [Bug 15456] New: No more login on Raspberry Pi 3 since 2023.02 bugzilla
2023-03-19 11:22 ` [Buildroot] [Bug 15456] " bugzilla
2023-03-19 13:50 ` bugzilla
2023-03-19 20:36 ` bugzilla [this message]
2023-03-21 19:25 ` bugzilla
2023-03-22 15:44 ` bugzilla
2023-03-24 16:32 ` bugzilla
2024-06-15 15:07 ` bugzilla

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-15456-163-o07RnUxNPi@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.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