Re: Memory corruptions in bc(1)

2015-11-20 Thread Sebastian Benoit
ok Otto Moerbeek(o...@drijf.net) on 2015.11.20 14:22:12 +0100: > On Fri, Nov 20, 2015 at 11:52:16AM +0100, Otto Moerbeek wrote: > > > On Thu, Nov 19, 2015 at 05:52:39PM -0500, Michael McConville wrote: > > > > > I'm already cache-thrashing with all of my side projects, so if anyone's > > > inter

Re: Memory corruptions in bc(1)

2015-11-20 Thread Otto Moerbeek
On Fri, Nov 20, 2015 at 11:52:16AM +0100, Otto Moerbeek wrote: > On Thu, Nov 19, 2015 at 05:52:39PM -0500, Michael McConville wrote: > > > I'm already cache-thrashing with all of my side projects, so if anyone's > > interested I'll leave this to them. > > > > A few days ago, I wanted to try Amer

Re: Memory corruptions in bc(1)

2015-11-20 Thread Otto Moerbeek
On Thu, Nov 19, 2015 at 05:52:39PM -0500, Michael McConville wrote: > I'm already cache-thrashing with all of my side projects, so if anyone's > interested I'll leave this to them. > > A few days ago, I wanted to try American Fuzzy Lop (afl), and bc(1) > seemed like a good first target: it pretty

Memory corruptions in bc(1)

2015-11-19 Thread Michael McConville
I'm already cache-thrashing with all of my side projects, so if anyone's interested I'll leave this to them. A few days ago, I wanted to try American Fuzzy Lop (afl), and bc(1) seemed like a good first target: it pretty much just goes from stdin to stdout, so there's no code reorganization needed.