bird-1.5.0 ipv4 segfaults on configure - is it safe to change bgp protocol names runtime?

[Jan Matejka]

On 03/18/2016 10:28 AM, Bartosz Radwan wrote:
> On 18.03.2016 10:07, Jan Matejka wrote:
>> Can you please send in a reduced config set that still causes this bug?
>> I'd like to reproduce it locally and fix it thereafter.
>>
>> Thanks a lot.
> Minimal config causing the errors:
> 
> protocol direct {
> 
>         interface "br0.*", "br1", "br1.*";
>         debug all;
> }
> protocol kernel {
>         learn;
>         persist;
>         scan time 1;
>         export all;
> }
> protocol device {
>         scan time 1;
> }
> protocol bgp one {
> 
>     router id 10.13.0.31;
>     debug all;
>     next hop self;
>     direct;
>     import none;
>     export filter { if net = 10.10.10.0/24 then {accept;  accept; }
> reject; };
>     local 10.13.0.1 as 65532;
>     neighbor 10.13.0.2 as 65531;
>     check link 1;
> }

Thanks!

> Testing this one ive got another segfault, seems quite random…:

There may be some broken code that stumps over random memory like a bull
in a china shop which causes segfault ... sometimes.

JM