Bird 2.0.0 -- unknown filter instructions
Hello *, I've been experimenting with bird 2.0.0 for a few days now. Apart from the memory leak (which Ondrej's patch appears to fix), the most serious issue I've run into is a spurious bird crash caused by the filter code. Twice so far, bird died when I ran 'birdc configure', with the messages "<BUG> Unknown instruction 26912" and "<BUG> Unknown instruction 0", respectively. I haven't been able to reliably reproduce these crashes, though. If someone has an idea how to do this, or at least how to narrow down which part of my lengthy filter config is causing it, that'd be much appreciated! Regards, Luis Ressel
Hello! On 12/16/2017 04:10 PM, Luis Ressel wrote:
I've been experimenting with bird 2.0.0 for a few days now. Apart from the memory leak (which Ondrej's patch appears to fix), the most serious issue I've run into is a spurious bird crash caused by the filter code. Twice so far, bird died when I ran 'birdc configure', with the messages "<BUG> Unknown instruction 26912" and "<BUG> Unknown instruction 0", respectively.
I haven't been able to reliably reproduce these crashes, though. If someone has an idea how to do this, or at least how to narrow down which part of my lengthy filter config is causing it, that'd be much appreciated! This seems to be some bad memory access. Please, if you can, send me your binary, config and coredump, off-list please as it may contain sensitive data.
There is no code setting these instruction codes intentionally. Thanks! Maria
On Sun, 17 Dec 2017 22:21:12 +0100 Jan Maria Matejka <jan.matejka@nic.cz> wrote:
This seems to be some bad memory access. Please, if you can, send me your binary, config and coredump, off-list please as it may contain sensitive data.
There is no code setting these instruction codes intentionally.
I've reconfigured my setup now so I can get usable core dumps. Let's hope bird crashes again soon. I ran into a third crash yesterday (opcode 56776) but I haven't been able to reproduce them reliably. What the all have in common is that they always occured after I changed a filter function and called birdc configure. Regards, Luis Ressel
participants (2)
-
Jan Maria Matejka -
Luis Ressel