Segfault in bird 2.0.5 when issuing "show ospf lsadb" from birdc

[aldem-bird.201704 at nk7.net]

Hi,

Attempt to show ospf's lsadb using birdc produces segfault, with or 
without ospf routes:

2019-08-29 20:04:39.203 <TRACE> device1: Initializing
2019-08-29 20:04:39.203 <TRACE> ospf1: Channel ipv4 connected to table 
master4
2019-08-29 20:04:39.203 <TRACE> ospf1: Initializing
2019-08-29 20:04:39.203 <TRACE> device1: Starting
2019-08-29 20:04:39.203 <TRACE> device1: State changed to up
2019-08-29 20:04:39.203 <INFO> Chosen router ID 192.168.255.4 according 
to interface failover
2019-08-29 20:04:39.203 <TRACE> ospf1: Starting
2019-08-29 20:04:39.203 <TRACE> ospf1: State changed to up
2019-08-29 20:04:39.203 <INFO> Started

# birdc
BIRD 2.0.5 ready.
bird> show ospf lsadb
Connection closed by server

Program received signal SIGSEGV, Segmentation fault.
0x000055555558b3d8 in ospf_sh_lsadb (ld=0x5555558c2ea0) at 
../proto/ospf/ospf.c:1455
1455      uint num = p->gr->hash_entries;
(gdb) list
1450
1451    void
1452    ospf_sh_lsadb(struct lsadb_show_data *ld)
1453    {
1454      struct ospf_proto *p = ld->proto;
1455      uint num = p->gr->hash_entries;
1456      uint i, j;
1457      int last_dscope = -1;
1458      u32 last_domain = 0;
1459      u16 type_mask = ospf_is_v2(p) ?  0x00ff : 0xffff;     /* see 
lsa_etype() */
(gdb) p p
$1 = (struct ospf_proto *) 0x0

In bird 2.0.4 everything is ok.

Seems that 2.0.5 has too many issues...

Best regards,
Alexander.