need help to understand winedebug options

[wildtux]

Hi,
There many options in winedebug and even I've read the dedicated page, I still not get how to use it to debug what I want to debug.

Is there someone that could explain what each winedebug options are?

[dimesio]

What is it you want to debug?

[wildtux]

Many things, I've build a Wine launcher/configurator and the all thing without a winedebug tab is not useless, but almost in my point of vue. That's why I need help to understand Winedbg options and how to manange.explain them in my winedebug tab.
I can manage options with this page https://wiki.winehq.org/Debug_Channels, but all channels usage is beyond my knowledge.

[Bob Wya]

Many things, I've build a Wine launcher/configurator and the all thing without a winedebug tab is not useless, but almost in my point of vue. That's why I need help to understand Winedbg options and how to manange.explain them in my winedebug tab.
I can manage options with this page https://wiki.winehq.org/Debug_Channels, but all channels usage is beyond my knowledge.

@wildtux,

Each wine debug channel typically covers one library or small group of related libraries - often implementing the API of a single Window dll.
Basically this feature is included so that you target the debug output from Wine - to a specific area that is problematic.
Otherwise you would get far to much noise.

If you don't understand what the channels mean...
Take a look at the Wine Source Code...
The Wine debug channel, for each Wine C source file, is declared near the top of the file.

Bob

[wildtux]

Sorry to be so late, I had some personnal issues and many fixes/things to do on my bash code.

Thanks Bob, I will check this. Hoping it will enlighten me

BTW, if you know some guys interested in bash code (meaning : not lost when reading a code), I severely need some help to fix my english grammar for tips text. Send them to github address below, they will be highly welcome.

https://github.com/wildtruc/winestart