Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] support/testing: new runtime test for bash
Date: Fri, 09 Jun 2023 11:09:21 +0200	[thread overview]
Message-ID: <87bkhp0zpa.fsf@48ers.dk> (raw)
In-Reply-To: <20230424215106.1202752-1-yann.morin.1998@free.fr> (Yann E. MORIN's message of "Mon, 24 Apr 2023 23:51:06 +0200")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

 > Commit 2dff6e93ca2a (package/readline: add upstream patch to fix crash
 > with invalid locale specification) fixed a regression in readline 8.2
 > [0], that could have been caught with a runtime test. readline is a
 > library, so we need an executable that exercises readline.

 > Since readline and bash are developped in tandem [1], it is only logical
 > to use bash to test readline.

 > Add a new runtime test for bash, that checks that we can indeed run an
 > interactive shell, and that an non-existing locale does not cause the
 > dreaded segfault. We do not use the default configuration, because it
 > uses a uclibc toolchain, and we want to reproduce against a glibc one.

 > [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021109
 > [1] https://tiswww.case.edu/php/chet/readline/rltop.html#Bugs

 > Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>

Committed to 2023.02.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2023-06-09  9:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-24 21:51 [Buildroot] [PATCH] support/testing: new runtime test for bash Yann E. MORIN
2023-05-08 21:53 ` Yann E. MORIN
2023-06-09  9:09 ` Peter Korsgaard [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=87bkhp0zpa.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=yann.morin.1998@free.fr \
    /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