On 2019-04-16 08:16:39, Paul Wise wrote:
> On Mon, 2019-04-15 at 13:21 -0400, Antoine Beaupré wrote:
>
>> Sure. Bisect tells me this one introduces the bug:
>
> Thanks for that.
>
>> I hope that helps.
>
> That commit fixes a pretty major bug, so I think that maybe the issue
> was present all along but masked by not using the right loop terminator.
>
> I think it would be interesting to do the bisect again but for each
> commit, cherry-pick the loop terminator fix before testing.
Ouch? Any practical way to do that?
It's kind of annoying there's no obvious way to automate the
reproducer. I tried to start it in tmux and it sometimes work, but not
reliably enough to automatically bisect...
And how would i reliable backport that patch systematically within
bisect anyways?
Thanks for any pointers...
a.
--
Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
- Benjamin Franklin, 1755
