Hello all, On Tue, Jun 09, 2026 at 07:28:39PM +0200, Marek Zarychta via Bird-users wrote:
> > unfortunately, BIRD 3.3.0 as shipped by EPEL 9 crashes at the following: > > > > $ birdc show route for 209.24.0.0/24 > > BIRD 3.3.0 ready. > > Connection closed by server > > > > The correct answer of above command should be "Network not found", which it > > is on at least BIRD 2.16. > > > > Btw, "birdc show route 209.24.0.0/24 filtered" crashes the same way on BIRD > > 3.3.0. The correct answer would also be "Network not found". That looks like a stupid oversight of myself. Unfortunately we have closed the merge window for 3.3.1 yesterday. We'll fix this in 3.3.2. > > Jun 9 18:34:52 systemd[1]: bird.service: Main process exited, code=dumped, > > status=11/SEGV > > > > > > But as "birdc show route for 1.1.1.1" and "birdc show route for 1.1.1.0/24" > > both work fine, this only seems to affect non-existing routes? > > > > Do you need anything else for debugging? Probably nothing, I already have my suspicions. > I can confirm that a FreeBSD build of BIRD 3.3.0 also crashes in this > scenario. This confirms to me that it's a straightforward bug in the logic, nothing crazy. Thank you for the report. I should have spotted this! -- Maria Matejka (she/her) | BIRD Team Leader | CZ.NIC, z.s.p.o.
