On 1/29/17 6:48 PM, Bruce Dubbs wrote:
> Bash Version: 4.4
> Patch Level: 0
> Release Status: release
>
> Description:
>
>When running regression tests on libinput, I get two different leaks
> identified by valgrind. The files below are not a part of libinput but are
> a part of bash.
What
This came up on comp.unix.shell:
There appears to be a parsing problem in bash where the sequence
$$'...' is treated as $'...', and $$"..." as $"...", when inside
$(...).
$ echo 'x\nx'
x\nx
$ echo $'x\nx'
x
x
$ echo $$'x\nx'
86293x\nx
$ echo $(echo $'x\nx')
x x
$ echo $(echo $$'x\nx')
x x
T
Chet Ramey wrote:
On 1/29/17 6:48 PM, Bruce Dubbs wrote:
Bash Version: 4.4
Patch Level: 0
Release Status: release
Description:
When running regression tests on libinput, I get two different leaks
identified by valgrind. The files below are not a part of libinput but are
a part of bash.
On 1/30/17 2:34 PM, Bruce Dubbs wrote:
>> xmalloc is a malloc wrapper, and `temp' is the return value from the
>> function.
>
> Yes, I know. The issue is that the caller, in this case set_default_locale
> or possibly main, never runs free on the allocated space. I tried to trace
> it in set_def
On 1/30/17 10:31 AM, Christian Weisgerber wrote:
> This came up on comp.unix.shell:
> There appears to be a parsing problem in bash where the sequence
> $$'...' is treated as $'...', and $$"..." as $"...", when inside
> $(...).
Yes, this is a problem. Thanks for the report. I've attached a one-l
Man page says:
When a shell with history enabled exits...
and
The shell exits by default upon receipt of a SIGHUP...
However on slower systems, at the end of the day when the user issues
the poweroff(8) command, all this might not complete, resulting in the
entire day's of history getting thr
