Re: Log format

On 7/14/20, U.Mutlu <[email protected]> wrote:
> [email protected] wrote on 07/14/2020 02:00 PM:
>>
>> I'd recommend you read through the documentation concerning the content
>> of
>> the log messages, which includes detail on how to further configure the
>> content thereof:https://www.privoxy.org/user-manual/config.html#DEBUGGING
>
> Thanks, Ian, but is there an error in the documentation in the debug values
>
> table: after 8192 comes 32768. Shouldn't that be rather 16384, etc. ?

It's probably not documented because you can't change it.

Take a look at
https://www.privoxy.org/gitweb/?p=privoxy.git;a=blob;f=errlog.h;h=5bfc16a5fd601df7cd7ba0973ffd454b9757cf1c;hb=HEAD#l38

16384 = 0x4000 = LOG_LEVEL_FATAL -- which is always enabled

> As I understand it the debug value is a 16-bit value, where the user can set
>
> any of the bits accordingly. Or is it a 32-bit value?

It's whatever the compiler says is an int (so probably a 32 bit value)
https://www.privoxy.org/gitweb/?p=privoxy.git;a=blob;f=errlog.h;h=5bfc16a5fd601df7cd7ba0973ffd454b9757cf1c;hb=HEAD#l76

https://www.privoxy.org/gitweb/?p=privoxy.git;a=blob;f=errlog.c;h=7cc4e200dcd938216e37b9cf7b247568e632afd2;hb=HEAD#l650

> But what about the mentioned 3rd value in the said log lines in my OP? What
> does it represent?

the thread id
https://www.privoxy.org/gitweb/?p=privoxy.git;a=blob;f=errlog.c;h=7cc4e200dcd938216e37b9cf7b247568e632afd2;hb=HEAD#l712

Regards,
Lee