Re: Documentation issue

2017-10-27 Thread Eli Barzilay
On Fri, Oct 27, 2017 at 2:37 AM, Clark Wang wrote: > > What `unset' does is special but there's nothing special when parsing > the command and bash even does not care if it's built-in command or > not. Exactly -- and this kind of a clarification is exactly the thing that many people are unaware o

Out-of-bounds read in parse_comsub()

2017-10-27 Thread Jakub Wilk
Machine: i686 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -g -Og -fsanitize=address -Wno-parentheses -Wno-format-security uname output: Linux debian 4.9.0-4-686-pae #1 SMP Debian 4.9.51-1 (2017-09-28) i686 GNU/Linux Machine Type: i686-pc-linux-gnu Bash Version: 20171020 snapshot Apparently

'fc' outputing text of DEBUG trap

2017-10-27 Thread Boruch Baum
In Debian, using Bash version 4.4, path level 12, I've set a DEBUG trap in my .bashrc and tried running the following command, with the following output resulting. The five lines between the command being run by fc and that command's output, is the text of the DEBUG trap. 1075 $ fc -e true 1072 1

Re: 'fc' outputing text of DEBUG trap

2017-10-27 Thread Eduardo Bustamante
On Fri, Oct 27, 2017 at 1:21 AM, Boruch Baum wrote: > In Debian, using Bash version 4.4, path level 12, I've set a DEBUG trap > in my .bashrc and tried running the following command, with the > following output resulting. The five lines between the command being run > by fc and that command's outp

Re: Out-of-bounds read in parse_comsub()

2017-10-27 Thread Eduardo A . Bustamante López
On Thu, Oct 26, 2017 at 11:07:57PM +0200, Jakub Wilk wrote: [...] > Bash Version: 20171020 snapshot > > Apparently an out-of-bounds read can happen in parse_comsub() when checking > script sytnax. To reproduce, rebuild bash with AddressSanitizer enabled and > run: > > $ printf > '$(00\177%012d

Re: Documentation issue

2017-10-27 Thread Chet Ramey
On 10/26/17 10:50 PM, Clark Wang wrote: > On Fri, Oct 27, 2017 at 3:00 AM, Eli Barzilay wrote: > >> On Thu, Oct 26, 2017 at 2:02 PM, Chet Ramey wrote: >>> >>> It's more of a general statement about arrays, though it appears in >>> the paragraph that discusses unset, so it's in the man page secti

Re: Out-of-bounds read in parse_comsub()

2017-10-27 Thread Chet Ramey
On 10/27/17 11:32 AM, Eduardo A. Bustamante López wrote: > On Thu, Oct 26, 2017 at 11:07:57PM +0200, Jakub Wilk wrote: > [...] >> Bash Version: 20171020 snapshot >> >> Apparently an out-of-bounds read can happen in parse_comsub() when checking >> script sytnax. To reproduce, rebuild bash with Addre