Profiling show that g_log() takes a lot of CPU even when logging isn't
authorAndersBroman <a.broman@bredband.net>
Thu, 8 May 2014 19:32:36 +0000 (21:32 +0200)
committerAnders Broman <a.broman58@gmail.com>
Thu, 8 May 2014 19:58:52 +0000 (19:58 +0000)
commitaa3a968eb6e85c47014a4cec4a2b955357b0e77f
tree3930086adcc70c0dc6882b18eacfd589ad06596a
parent379c9f25dfb71217a7cfec02e7e949b60d556b7f
Profiling show that g_log() takes a lot of CPU even when logging isn't
active.

Change-Id: I242f8e98a77861c0174e432c7026964babae7299
Reviewed-on: https://code.wireshark.org/review/1565
Reviewed-by: Anders Broman <a.broman58@gmail.com>
dumpcap.c