On 12 April 2017 at 13:47, Reuben Thomas <r...@sc3d.org> wrote: > > > I guess one further option is to fix the bug in bash, and then call > valgrind with --trace-children=yes. Maybe that would be cleanest and > simplest (albeit we'll need a workaround until fixed bash is widely > available). >
I tested bash 4.4, and got exactly the same problem. I see there's a Debian bug open for this issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849517 I get the bug if I do a build of bash from GNU sources (i.e. it doesn't seem to be a Debian patch causing the problem). I can't find anything about this in the bug-bash archives (there is discussion of other valgrind diagnostics, but not this one), so I've reported a bug there. -- http://rrt.sc3d.org
