Re: Segmentation fault on 2.0.5

2019-08-13 Thread Radu Anghel
On 13.08.2019 17:45, Maria Jan Matejka wrote: define myvar = false; function something () { if myvar then { return false; } return true; } protocol device DEVICE { } Could this be because of the new filter code or something else? Hello Thanks for bugreport. Yes, it

Re: Segmentation fault on 2.0.5

2019-08-13 Thread Maria Jan Matejka
>> define myvar = false; >> >> function something () { >> if myvar then { >> return false; >> } >> >> return true; >> } >> >> protocol device DEVICE { >> >> } >> >> Could this be because of the new filter code or something else? > > Hello > > Thanks for bugreport. Yes, it is t

Re: Segmentation fault on 2.0.5

2019-08-10 Thread Ondrej Zajicek
On Sat, Aug 10, 2019 at 02:22:18PM +0300, Radu Anghel wrote: > Hello, > > I recently upgraded BIRD from 2.0.4 to 2.0.5 and with the same (pretty > large) .conf I got Segmentation fault. > > Until today I didn't have time to debug it, but here it goes: > > With this simple .conf I get seg fault o

Segmentation fault on 2.0.5

2019-08-10 Thread Radu Anghel
Hello, I recently upgraded BIRD from 2.0.4 to 2.0.5 and with the same (pretty large) .conf I got Segmentation fault. Until today I didn't have time to debug it, but here it goes: With this simple .conf I get seg fault on 2.0.5 while 2.0.4 works as expected. (if I define myvar = true it doesn't c