On Thu, Aug 29, 2019 at 08:08:23PM +0200, aldem-bird.201704@nk7.net wrote:
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
Hi Thanks for the bugreport, patch is attached. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."