On Sun, Jun 5, 2016 at 8:48 PM, Chet Ramey wrote:
> "Traced functions inherit the DEBUG and RETURN traps from the calling
> shell."
Why did RETURN originally get sucked into set -T? Was it supposed to
be primarily for debugging? Some functions actually use it for
internal purposes and enabl
On 6/2/16 2:43 PM, Carlos Morata wrote:
> Hi,
>
> I think you misunderstod me.
> I'm really interested in working with relative command history expasions.
> So I need to work with !-$((\#-cmdnumbertarget)), not with !$HISTCMD.
>
> I figure it out pretty well already but I think this is a bug caus
(Chet, your specific attention is required for this email, please)
Ximin Luo:
> On Sat, 28 May 2016 13:38:35 +0200 Reiner Herrmann wrote:
>> After that, the only remaining issue is that the included header file
>> /usr/include/bash/config.h varies depending on the kernel version used
>> during bu
On 6/5/16 9:10 AM, Jason Vas Dias wrote:
> With a build of bash 4.3 patchlevel 42
> on a Linux x86_64 system I am getting
> warning messages on stderr when
> running a certain script like:
>"wait_for: no record of process 8278" .
> Running bash with the script as
> input under strace shows that
On 6/2/16 9:20 AM, Paulo César Pereira de Andrade wrote:
> Hi,
>
> This is a "RFC" to update documentation to better match behavior,
> or, to get some information about shell tracing.
>
> Bellow I am quoting a request from an user:
>
> ---8<---
> The bash shell offers the xtrace (set -x),
On 6/2/16 7:08 AM, Grisha Levit wrote:
> These are maybe similar to the less-interesting issue of namerefs pointing
> to array subscripts, but are triggered by relatively normal assignments:
All the same problem, with the same fix: accurately reproducing the
original name and assignment statement
On 6/1/16 10:45 PM, Grisha Levit wrote:
> I guess it’s even more general than just list assignments. See also below
> problems with |declare|:
These are all the same problem, and the same as the previous report.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ar
OK, I found one fix - you probably
won't like it, but it fixes the oroblem,
and all the test cases run in
'make test' still work - especially
'run_jobs' and 'run_lastpipe' -
the patch simply removes the error
from the FIND_CHILD macro in jobs.c,
so it noe reads ;
jobs.c @ line 2377:
#define FIND_C
The strace log shows that process 8277 is the
bash subshell that runs f() , forks to create 8278,
which forks to execve "some_executable" ;
process 8277 then eads the 8278 output on a pipe,
so it knows when the pipe is closed, amd the strace
log shows 8277 first does a wait4, which returns 8278,
b
With a build of bash 4.3 patchlevel 42
on a Linux x86_64 system I am getting
warning messages on stderr when
running a certain script like:
"wait_for: no record of process 8278" .
Running bash with the script as
input under strace shows that process 8277
does a successful wait4(-1,...) which DOE
10 matches
Mail list logo
