Hi,
Is there a way to change the trace options of WINEDEBUG during runtime? For example, let's say I'm running an installer that encounters a fatal error during one part of the install. I'm not exactly sure where in the wine code base this error is occurring and it would take forever if I set WINEDEBUG=trace+all and had to wait till I get to the right section to find the error. If this is not a feature we have, would it be possible to write a simple program that will send a message to the wineserver telling it to change it's WINEDEBUG value during runtime? I have no idea how this would be implemented or if anyone else would actually want this feature, but if you have any ideas let me know. Thanks.
James Hawkins wrote:
Hi,
Is there a way to change the trace options of WINEDEBUG during runtime?
WINEDEBUG=trace+all wine setup.exe 2>&1 | sed '1,/Debug mark/d'
Then you just need to bring the system menu up and click on "Put 'Debug mark' in debug log" and debugging will then start. I seem to remember that Mike Hearn submitted a patch a while ago that did exactly what you are asking for, but Alexandre rejected it saying that it could be done just as easily with external programs. I just haven't figured out how yet...
Rob
Le mer 25/08/2004 à 17:29, Robert Shearman a écrit :
James Hawkins wrote:
Hi,
Is there a way to change the trace options of WINEDEBUG during runtime?
WINEDEBUG=trace+all wine setup.exe 2>&1 | sed '1,/Debug mark/d'
Then you just need to bring the system menu up and click on "Put 'Debug mark' in debug log" and debugging will then start. I seem to remember that Mike Hearn submitted a patch a while ago that did exactly what you are asking for, but Alexandre rejected it saying that it could be done just as easily with external programs. I just haven't figured out how yet...
ReactOS taskmgr (programs/taskmgr) can do that for any channel, although I didn't see the "all" debug channel.
Vincent
Then you just need to bring the system menu up and click on "Put 'Debug mark' in debug log" and debugging will then start.
I'm not exactly sure what you mean by system menu. I cant remember seeing the "Put...log" anywhere. Thankyou for your help on this response btw.
On 25 Aug 2004 18:40:22 -0400, Vincent Béron vberon@mecano.gme.usherb.ca wrote:
Le mer 25/08/2004 à 17:29, Robert Shearman a écrit :
James Hawkins wrote:
Hi,
Is there a way to change the trace options of WINEDEBUG during runtime?
WINEDEBUG=trace+all wine setup.exe 2>&1 | sed '1,/Debug mark/d'
Then you just need to bring the system menu up and click on "Put 'Debug mark' in debug log" and debugging will then start. I seem to remember that Mike Hearn submitted a patch a while ago that did exactly what you are asking for, but Alexandre rejected it saying that it could be done just as easily with external programs. I just haven't figured out how yet....
ReactOS taskmgr (programs/taskmgr) can do that for any channel, although I didn't see the "all" debug channel.
Vincent
Le mer 25/08/2004 à 19:11, James Hawkins a écrit :
Then you just need to bring the system menu up and click on "Put 'Debug mark' in debug log" and debugging will then start.
I'm not exactly sure what you mean by system menu. I cant remember seeing the "Put...log" anywhere. Thankyou for your help on this response btw.
[snip]
I didn't see it when used in "Managed"="Y" mode, but with "Managed"="N" the option's there (Alt-space, or the icon in the top-left corner of the window of the app).
Vincent
Oh ok thanks a bunch I will definitely try it out now.
On 25 Aug 2004 19:25:19 -0400, Vincent Béron vberon@mecano.gme.usherb.ca wrote:
Le mer 25/08/2004 à 19:11, James Hawkins a écrit :
Then you just need to bring the system menu up and click on "Put 'Debug mark' in debug log" and debugging will then start.
I'm not exactly sure what you mean by system menu. I cant remember seeing the "Put...log" anywhere. Thankyou for your help on this response btw.
[snip]
I didn't see it when used in "Managed"="Y" mode, but with "Managed"="N" the option's there (Alt-space, or the icon in the top-left corner of the window of the app).
Vincent
I ran WINEDEBUG=trace+all wine setup.exe 2>&1 | sed '1,/Debug mark/d' in the terminal, and all of the debug output is being displayed already without selecting the "Put..log" option. I switched "Managed" to "N" at Vincent's suggestion. Any ideas?
On Wed, 25 Aug 2004 19:34:34 -0400, James Hawkins truiken@gmail.com wrote:
Oh ok thanks a bunch I will definitely try it out now.
On 25 Aug 2004 19:25:19 -0400, Vincent Béron
vberon@mecano.gme.usherb.ca wrote:
Le mer 25/08/2004 à 19:11, James Hawkins a écrit :
Then you just need to bring the system menu up and click on "Put 'Debug mark' in debug log" and debugging will then start.
I'm not exactly sure what you mean by system menu. I cant remember seeing the "Put...log" anywhere. Thankyou for your help on this response btw.
[snip]
I didn't see it when used in "Managed"="Y" mode, but with "Managed"="N" the option's there (Alt-space, or the icon in the top-left corner of the window of the app).
Vincent
-- James Hawkins
James Hawkins wrote:
I ran WINEDEBUG=trace+all wine setup.exe 2>&1 | sed '1,/Debug mark/d' in the terminal, and all of the debug output is being displayed already without selecting the "Put..log" option. I switched "Managed" to "N" at Vincent's suggestion. Any ideas?
Try this instead:
WINEDEBUG=trace+all wine setup.exe 2>&1 | sed '1,/Debug mark requested/d'
It then shouldn't match against a call to the menu functions that put the debug log option into the system menu.
Rob
Oh ok thanks Rob I'll try it out.
On Thu, 26 Aug 2004 01:49:41 +0100, Robert Shearman rob@codeweavers.com wrote:
James Hawkins wrote:
I ran WINEDEBUG=trace+all wine setup.exe 2>&1 | sed '1,/Debug mark/d' in the terminal, and all of the debug output is being displayed already without selecting the "Put..log" option. I switched "Managed" to "N" at Vincent's suggestion. Any ideas?
Try this instead:
WINEDEBUG=trace+all wine setup.exe 2>&1 | sed '1,/Debug mark requested/d'
It then shouldn't match against a call to the menu functions that put the debug log option into the system menu.
Rob
James Hawkins wrote:
Oh ok thanks Rob I'll try it out.
I tend to find piping stuff through sed is too slow (but then I have quite a slow computer). There is a patch floating around in the archives that lets you toggle debug logging on and off using the F12 key. It works at the level of the debug infrastructure itself so the app speeds up noticeably when it's not doing lots of printfs.
It may have bitrotted. Alexandre wouldn't apply it, as it put policy into the Wine core (at least, if I remember correctly).
FWIW I usually find +all traces give too much output for debugging anything other than startup problems where you have no idea what's wrong. Beyond a few seconds execution the logs get too big to work with, especially if you're working blind.
Mike Hearn wrote:
FWIW I usually find +all traces give too much output for debugging anything other than startup problems where you have no idea what's wrong. Beyond a few seconds execution the logs get too big to work with, especially if you're working blind.
And also, as I reported on bug #2393, seems like RelayExclude doesn't work, so the allocate/free heap and the enter/leave critical section messages fills the output so much that it's impossible to use it for debug. Trying to tracing ClrMamePro I'm having a log of 3Gb right after the first window is loaded...
Vincent Béron wrote:
I didn't see it when used in "Managed"="Y" mode, but with "Managed"="N" the option's there (Alt-space, or the icon in the top-left corner of the window of the app).
When an app is running in Managed Mode we can access the system menu opening the first menu (usually File) and then moving to left (so the previous menu, which is the system menu :) ).
-
Diego 'Flameeyes' Pettenò -
James Hawkins -
Mike Hearn -
Robert Shearman -
Vincent Béron