7 Bug-Reported-by: Andrew Neff <andrew.neff@visionsystemsinc.com>
8 Bug-Reference-ID: <SA1P110MB1357F68AFD51BB225019EFF48D2B9@SA1P110MB1357.NAMP110.PROD.OUTLOOK.COM>
9 Bug-Reference-URL: https://lists.gnu.org/archive/html/bug-bash/2022-10/msg00100.html
13 Make sure a subshell checks for and handles any terminating signals before
14 exiting (which might have arrived after the command completed) so the parent
15 and any EXIT trap will see the correct value for $?.
17 Patch (apply with `patch -p0'):
19 *** ../bash-5.2.9/execute_cmd.c 2022-11-02 10:36:54.000000000 -0400
20 --- execute_cmd.c 2022-10-27 16:52:55.000000000 -0400
26 + /* Check for terminating signals before we return to our caller, which we
27 + expect to exit immediately anyway. */
30 /* If we were explicitly placed in a subshell with (), we need
32 *** ../bash-5.2/patchlevel.h 2020-06-22 14:51:03.000000000 -0400
33 --- patchlevel.h 2020-10-01 11:01:28.000000000 -0400
36 looks for to find the patch level (for the sccs version string). */
38 ! #define PATCHLEVEL 24
40 #endif /* _PATCHLEVEL_H_ */
42 looks for to find the patch level (for the sccs version string). */
44 ! #define PATCHLEVEL 25
46 #endif /* _PATCHLEVEL_H_ */