Comment 15 for bug 1818211

I agree that previously it looks as if the files failed to compile and as a result were ignored with the annoying side effect of the error messages coming out on stderr and appearing in places they shouldn't.

I think that it's more than a little worrying that it's possible for uploaded .yar files to take out a running production clamd daemon.

I would like to be able to compile the code with NDEBUG off - so that the assertions in the code don't trigger the abort signal. I've never had to get to grips with configure - it seems to always define NDEBUG as on - even when --enable-debug is not included.

I tried --enable-debug=no which theoretically should do reverse the sense of the option, but to no avail.

There does seem to be considerable magic involved with the setting of debug flags in the compilation system.