Daniel Santos daniel.santos@pobox.com writes:
Currently, if any classes are passed to WINEDEBUG (nb_debug_options > 0) then the initial lazy-init call to __wine_dbg_get_channel_flags() never sets the flags in the struct __wine_debug_channel in the object file, resulting in all 45k trace calls in wine making a function call, running bsearch on debug_options with string compare, etc.
Not really. Only the channel that is actually enabled will make repeated function calls. This is done on purpose so that you can toggle it on and off for a given process from the task manager.
On 09/01/2015 07:10 AM, Alexandre Julliard wrote:
Daniel Santos daniel.santos@pobox.com writes:
Currently, if any classes are passed to WINEDEBUG (nb_debug_options > 0) then the initial lazy-init call to __wine_dbg_get_channel_flags() never sets the flags in the struct __wine_debug_channel in the object file, resulting in all 45k trace calls in wine making a function call, running bsearch on debug_options with string compare, etc.
Not really. Only the channel that is actually enabled will make repeated function calls. This is done on purpose so that you can toggle it on and off for a given process from the task manager.
My apologies for the oversight! I wish I had known about task manager toggle ability before I updated the debug F12 toggle key patch set. I see that this is described in the Developer's Guide, but I didn't find anything in the wiki about it. I guess I'll play with this a little bit and then add some information about this to the wiki page http://wiki.winehq.org/DebugChannels.
-
Alexandre Julliard -
Daniel Santos