Debugging named function filters properly

Ondrej Zajicek santiago at crfreenet.org
Mon Jun 14 15:04:23 CEST 2021


On Sat, Jun 12, 2021 at 10:15:54AM +0300, Skyler Mäntysaari wrote:
> Hi there,
> 
> How does one debug filters properly as I'm getting lots of:
> 2021-06-12 09:02:35 <ERR> filters, line 82: Argument 1 of instruction
> FI_CONDITION must be of type T_BOOL, got 0x00
> 2021-06-12 09:02:35 <ERR> filters, line 452: Argument 1 of instruction
> FI_CONDITION must be of type T_BOOL, got 0x00
> 
> in logs, but I need it to say which function that is or even file, so how
> would I debug this properly? Just "debug { filters; }" doesn't help much.

Hi

There are line numbers (82, 452). Filename is missing. Reporting function
seems like a good idea, will think about that.

-- 
Elen sila lumenn' omentielvo

Ondrej 'Santiago' Zajicek (email: santiago at 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."



More information about the Bird-users mailing list