Re: Release date for Privoxy 3.0.24

On 1/21/2016 1:48 PM, Fabian Keil wrote:
> While I'm having trouble parsing the comment as well, I interpret it similarly.
> I assume David meant to write "discernible" or "distinguishable" or something
> like this and was using a 32 bit system which is relevant for the "4 bytes" part.

I wrote that comment. :-)  'debuggable' literally meant just that.  If 
you wanted to attach gdb, for example, you'd want to know which process 
ID to attach to... but of course we're talking about threads, not 
processes.  So debuggability is actually moot here.

The idea was simply to make the thread ID look somewhat presentable as a 
number, and still have a reasonable chance of not colliding with another 
similarly truncated thread ID (in Privoxy).  The Mach kernel has a very 
chatty thread ID, so I was just trying to reduce clutter in the log.

- David

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140