Re: Running bash under valgrind gives "invalid free()"

On 4/12/17 12:58 PM, Hanno Böck wrote: > On Wed, 12 Apr 2017 14:59:26 +0100 > Reuben Thomas wrote: > >> ​frequently, it's the only tool that shows up bugs of this sort, as >> it's rather more powerful than a debugging malloc library.) > > Try address sanitizer, it's pretty reliable and finds eve

Re: Running bash under valgrind gives "invalid free()"

On Wed, 12 Apr 2017 14:59:26 +0100 Reuben Thomas wrote: > ​frequently, it's the only tool that shows up bugs of this sort, as > it's rather more powerful than a debugging malloc library.) Try address sanitizer, it's pretty reliable and finds even more bug classes compared to valgrind. Just add -

Re: Running bash under valgrind gives "invalid free()"

On Apr 12, 2017 4:56 PM, "Chet Ramey" wrote: [snip] > Maybe update the Debian bug report you cited as well. There's still stuff > there from 2005. The report is from December 2016. I can't find "2005" in the page. I'll certainly send an update to point to the upstream bug I file.

Re: Running bash under valgrind gives "invalid free()"

On 4/12/17 10:59 AM, Reuben Thomas wrote: > ​O​ > n 12 April 2017 at 15:49, Chet Ramey > wrote: > > > It's a false positive, or a bug in valgrind. I took a quick look. There's > one place in this code path where free() gets called. Here's the trace: > > >

Re: Running bash under valgrind gives "invalid free()"

​O​ n 12 April 2017 at 15:49, Chet Ramey wrote: > > It's a false positive, or a bug in valgrind. I took a quick look. There's > one place in this code path where free() gets called. Here's the trace: > ​[analysis snipped] Thanks very much, looks like it's time for me to file a Valgrind bug re

Re: Running bash under valgrind gives "invalid free()"

On 4/12/17 9:59 AM, Reuben Thomas wrote: > ​O​ > n 12 April 2017 at 14:50, Chet Ramey > wrote: > > On 4/12/17 8:57 AM, Reuben Thomas wrote: > > See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849517 >

Re: Running bash under valgrind gives "invalid free()"

​O​ n 12 April 2017 at 14:50, Chet Ramey wrote: > On 4/12/17 8:57 AM, Reuben Thomas wrote: > > See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849517 > > > > ​I can reproduce this also in bash 4.3 as supplied with Ubuntu 16.04, and > > in a build of 4.4 from source on my Ubuntu system. > >

Re: Running bash under valgrind gives "invalid free()"

On 4/12/17 8:57 AM, Reuben Thomas wrote: > See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849517 > > ​I can reproduce this also in bash 4.3 as supplied with Ubuntu 16.04, and > in a build of 4.4 from source on my Ubuntu system. > > ​As stated in the bug report, the bug causes problems beyo

Re: The clean opt can not delete all objs(like *.o)

On 4/12/17 3:27 AM, chrlis wrote: > I find a special case: > ->cd bash-4.4 > ->mkdir build > ->cd build > ->... > ->make clean > > When I make clean current building directory, it never remove the object > 'man2html.o' in the path /path/to/build/support. > Is this a problem ? Thanks for the repor

Running bash under valgrind gives "invalid free()"

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849517 ​I can reproduce this also in bash 4.3 as supplied with Ubuntu 16.04, and in a build of 4.4 from source on my Ubuntu system. ​As stated in the bug report, the bug causes problems beyond bash, as it causes build systems to think that val

The clean opt can not delete all objs(like *.o)

I find a special case: ->cd bash-4.4 ->mkdir build ->cd build ->... ->make clean When I make clean current building directory, it never remove the object 'man2html.o' in the path /path/to/build/support. Is this a problem ? The released bash source code version is: https://ftp.gnu.org/gnu/bash