<html><head></head><body>Hello!<br><br>Before I try to get some MIPS to check this issue, could you please send me your binary and core file? It should be analyzable on my amd64 desktop.<br><br>Anyway, inspecting the ROA table by show route command should work and this is definitely a bug.<br><br>Thank you for the report!<br>Maria<br><br><div class="gmail_quote">On November 5, 2018 2:47:36 AM GMT+01:00, Clemens Schrimpe <clemens.schrimpe@gmail.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">Hello -<br><br>just wanted to report a little (easily reproducable) problem: I’m experimenting with BIRD 2.0.2 on a lab-router (Ubiquiti Edgerouter, MIPS platform) and RPKI. <br><br>In my attempts to examine ROA tables more closely I entered „show route table r4 all“ into birdc and bird immediately segfaulted and died.<br><br>Is there any „official“ way to examine the contents of ROA tables other than „eval roa_check(r4, 186.255.72.0/24, 204777)“?<br><br>I would have assumed „show route table r4 all 186.255.72.0/24“ or something like that would work, but it doesn’t (gives empty output). At least „show route table r4 count“ gives useful information, though.<br><br>Thanks,<br><br> Clemens<br><br><br></pre></blockquote></div><br>-- <br>Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html>