Re: [exim] issue with ${reduce and ${extract

2017-02-26 Thread Jeremy Harris
On 26/02/17 12:04, Phil Pennock wrote: > On 2017-02-26 at 13:24 +0200, Victor Ustugov wrote: >> Phil Pennock wrote: >>> I'm perplexed. Either my bisect run-script is bad, >> >> So, is this bisect run-script useless and I may skip it? > > Nope, the script is good. :-( > > https://bugs.exim.org/s

Re: [exim] issue with ${reduce and ${extract

2017-02-26 Thread Phil Pennock
On 2017-02-26 at 13:24 +0200, Victor Ustugov wrote: > Phil Pennock wrote: > > I'm perplexed. Either my bisect run-script is bad, > > So, is this bisect run-script useless and I may skip it? Nope, the script is good. :-( https://bugs.exim.org/show_bug.cgi?id=2061 Reverting that commit resolves

Re: [exim] issue with ${reduce and ${extract

2017-02-26 Thread Phil Pennock via Exim-users
On 2017-02-25 at 22:25 -0500, Phil Pennock wrote: > 20fcb1e7be45177beca2d433f54260843cc7c2f6 is the first bad commit > commit 20fcb1e7be45177beca2d433f54260843cc7c2f6 > At this point, I suspect that the issue is the current line 4974 of > expand.c, where `lookup_value = NULL` while skipping, but i

Re: [exim] issue with ${reduce and ${extract

2017-02-26 Thread Victor Ustugov
Hello, Phil. Thanks for your reply. Phil Pennock wrote: > On 2017-02-25 at 22:25 -0500, Phil Pennock wrote: >> 20fcb1e7be45177beca2d433f54260843cc7c2f6 is the first bad commit >> commit 20fcb1e7be45177beca2d433f54260843cc7c2f6 > >> At this point, I suspect that the issue is the current line 4974