On 8/14/17 2:50 AM, GwanYeong Kim wrote:
> Hello,
>
> I found a Null Pointer Dereference bug in bash.
>
> Please confirm.
I can't reproduce it with the current development version.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis''
On 8/11/17 6:55 PM, Matthew Persico wrote:
> What I propose to do between steps 2 and 3 is
>
> 2.1 - After sourcing the function in, type the function to get its text
> 2.2 - type appears to pretty print function code. No matter how sloppy or
> compact your function is on disk, type presents it t
Holy crap there is some nasty stuff in that script.
You can try shopt -s checkwinsize to see if that helps
On Mon, Aug 14, 2017 at 9:06 AM, Ángel wrote:
> On 2017-08-10 Leon Klingele wrote:
> > Is this problem caused by bash?
> >
> Most likely, something done by fzf is not "completely right" as
Hello,
I found a Null Pointer Dereference bug in bash.
Please confirm.
Thanks.
Version: bash 4.4.12(1)-maint(cb8c37dc664c2c0c12772111d3cc3a560d50cb04)
OS: Ubuntu 16.04.2 64bit
Steps to reproduce:
1.Download the PoC files.
2.Execute the following command
: ./bash $PoC
```
ASAN:SIGSEGV
On 2017-08-10 Leon Klingele wrote:
> Is this problem caused by bash?
>
Most likely, something done by fzf is not "completely right" as in fzf
sets up things in a way that bash is then unable to determine the right
width of the line it was asked to print.
I guess the sourced file corresponds to th