On Mon, Dec 28, 2020 at 06:47:29PM +0100, Damian Zaremba wrote: > Hi, > > Thanks for the fast response and fix - I can confirm that is working as > expected on my side. > > Unfortunately I did discover another segfault (testing from current master) > which appears to be due to `net` being uninitialised in the route specific > filters;
> This was originally triggered in a function call that used an `if net ~ set` > operation, so while the above config doesn't really make practical sense > it's the smallest filter I could make to repeatedly trigger the issue. > > I suspect my interpretation of the per-route filter expression support is a > little too liberal compared to the intended usage. Well, this is something that likely should work (or at least not crash). Will check that. Seems like per-route filters are undertested feature. > For now I will go back to applying filtering on a pipe from one "static > table" into another "static table", which should solve my needs, but I > wanted to highlight the second crash as it's not ideal behavior. You could probably just do that in import filter of the static protocol. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: [email protected]) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
