On 2/5/24 12:22 PM, Mykyta Dorokhin wrote:
Note 1: forgot to mention that I'm cross-compiling.
Note 2: it probably makes sense to add a warning or something that states
that HAVE_POSIX_SIGSETJMP disabled due to cross-compiling.
The autoconf macro that tests for this (BASH_FUNC_POSIX_SETJMP)
On 2/3/24 7:01 PM, Mykyta Dorokhin wrote:
There is a line in trap.c with your change. If I revert it then everything
works again:
- if (interrupt_immediately && wait_intr_flag)
+ if (/* interrupt_immediately && */wait_intr_flag)
So if I put interrupt_immediately back and rebuild the code
On 2/3/24 10:28 AM, Mykyta Dorokhin wrote:
Analysis with strace.
After receiving SIGUSR1, Debian only blocks SIGCHLD, then clears the block:
205295 --- SIGUSR1 {si_signo=SIGUSR1, si_code=SI_USER, si_pid=205327,
si_uid=1040} ---
205295 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
205295
On 2/3/24 10:00 AM, Mykyta Dorokhin wrote:
I have found the commit on devel branch which breaks things for me (and
probably other Yocto-based builds):
This one still works
==
commit 89d788fb0152724a93e0fdab8c15116e5c76572b
Author: Chet Ramey
Date: Mon Feb 17 11:41:35
On 1/5/24 2:46 PM, Mykyta Dorokhin wrote:
Bash Version: 5.1
Patch Level: 16
Release Status: release
Description:
I'm working on a custom project within the Yocto framework. After a recent
build system update, the bash
version updated to 5.1.16. Subsequently, I've noticed peculiar side
