On 11/22/22 5:04 PM, Dabrien 'Dabe' Murphy wrote:
On 11/22/22 5:01 PM, Chet Ramey wrote:
Thanks for the report. It's an easy fix; bash was optimizing away the fork
and therefore not printing the timing information.
Awesome!
Hitting it with a hammer: $10
Knowing WHERE to hit it:
On 11/21/22 9:36 PM, Dabrien 'Dabe' Murphy wrote:
More crumbs, FTR:
19:51 this comment looks very suspicious
https://git.savannah.gnu.org/cgit/bash.git/diff/execute_cmd.c?h=devel=9928dcb48f35d957d936f9c6d8bec8cec8b76317
19:52 that patch addresses this bug
On 11/22/22 5:01 PM, Chet Ramey wrote:
Thanks for the report. It's an easy fix; bash was optimizing away the
fork
and therefore not printing the timing information.
Awesome!
Hitting it with a hammer: $10
Knowing WHERE to hit it: $9,990
«grin»
--
:- Dabe
On 11/21/22 7:07 PM, d...@dabe.com wrote:
Bash Version: 5.2
Patch Level: 9
Release Status: release
Description:
Under 5.2.x, measuring the `time` of a subshell -- `time ( sleep 1 )`
for example -- doesn't display any timing information,
whereas `5.1.x` and before did.
On 11/21/22 9:32 PM, Koichi Murase wrote:
`git bisect' finds the following commit (2022-01-31) which introduced
the behavior:
commit b325b0e96bd05c76bbfc4d60d0707fc93d58f03f (HEAD, refs/bisect/bad)
execute_cmd.c
- execute_in_subshell: call optimize_subshell_command for (list)
2022年11月22日(火) 9:36 Emanuele Torre :
> No, actually later, I said that it has probably been introduced earlier
> since I tried running 'time (sleep 1)' in a version of bash that
> preceeds that change (namely 6711d2dc7793ed3d35e91b2bd4ecbdfccfcf469f
> (2022-10-24)), and it still didn't print the
On 11/21/22 7:36 PM, Emanuele Torre wrote:
On Mon, Nov 21, 2022 at 07:07:08PM -0500, d...@dabe.com wrote:
emanuele6 suspects it has to do with
https://lists.gnu.org/archive/html/bug-bash/2022-10/msg00107.html
No, actually later, I said that it has probably been introduced earlier
On Mon, Nov 21, 2022 at 07:07:08PM -0500, d...@dabe.com wrote:
> emanuele6 suspects it has to do with
> https://lists.gnu.org/archive/html/bug-bash/2022-10/msg00107.html
No, actually later, I said that it has probably been introduced earlier
since I tried running 'time (sleep 1)' in a
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: darwin22.1.0
Compiler: clang
Compilation CFLAGS: -DSSH_SOURCE_BASHRC
uname output: Darwin triton.parabon.com 22.1.0 Darwin Kernel Version 22.1.0:
Sun Oct 9 20:14:54 PDT 2022;
