Changing debug channels on the fly
It looks like programs/taskmgr/taskmgr used to let you edit debug channels for any process, but now that function seems broken; when I right-click on a process and select 'edit debug channels', I get column headers Debug Channel Fixme Err Warn Trace but nothing under them. Is this supposed to work? In the meantime, I'll make do with http://wiki.winehq.org/Debug_trace_toggle_key which is kind of what I was looking for anyway.
Am Freitag 06 April 2007 01:33 schrieb Dan Kegel:
It looks like programs/taskmgr/taskmgr used to let you edit debug channels for any process, but now that function seems broken; when I right-click on a process and select 'edit debug channels', I get column headers Debug Channel Fixme Err Warn Trace but nothing under them. Is this supposed to work? I think you have to enable the channels when starting, you can deaktivate them afterwards. Not that I ever had luck with it though :-(
While the functionality you mentioned might be broken at the moment the following might also be useful: http://wiki.winehq.org/Debug_trace_toggle_key The patch adds a key using which you can enable/disable debugmessages.
It looks like programs/taskmgr/taskmgr used to let you edit debug channels for any process, but now that function seems broken; when I right-click on a process and select 'edit debug channels', I get column headers Debug Channel Fixme Err Warn Trace but nothing under them. Is this supposed to work?
In the meantime, I'll make do with http://wiki.winehq.org/Debug_trace_toggle_key which is kind of what I was looking for anyway.
Regards, Roderick -- "Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ... Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail
On Fri, Apr 06, 2007 at 09:09:18AM +0200, Roderick Colenbrander wrote:
While the functionality you mentioned might be broken at the moment the following might also be useful: http://wiki.winehq.org/Debug_trace_toggle_key
The patch adds a key using which you can enable/disable debugmessages.
I enhanced that a bit and have a patch based on a recent winehq git: http://repo.or.cz/w/wine/hacks.git?a=commit;h=a3840322693b5630bf8ffd7f85e928... Jan
On 4/6/07, Roderick Colenbrander <thunderbird2k(a)gmx.net> wrote:
It looks like programs/taskmgr/taskmgr used to let you edit debug channels for any process, but now that function seems broken... In the meantime, I'll make do with http://wiki.winehq.org/Debug_trace_toggle_key
While the functionality you mentioned might be broken at the moment the following might also be useful: http://wiki.winehq.org/Debug_trace_toggle_key
Yes, I tried that. It doesn't control +relay, though, and you can only toggle the process that's listening to the keyboard, which isn't very helpful in general. - Dan
Jan wrote:
I enhanced that a bit and have a patch based on a recent winehq git: http://repo.or.cz/w/wine/hacks.git?a=commit;h=a3840322693b5630bf8ffd7f85e928...
Thanks, but like the original, it doesn't control +relay, nor does it help with processes that aren't listening to the keyboard. Also, I have my doubts about this code: + static int first = 0; + + if( first && !block_traces && getenv("WINEDELAY") && 0 == strncasecmp(getenv("WINEDELAY"), "enable", 6) ) { + wine_dbg_toggle_block(); + first = 1; + } It looks like there's a typo; shouldn't first be initialized to 1 and then set to zero after first run? As it is, that code seems to never fire. Can I get your opinion on my alternate patch, described at http://www.winehq.org/pipermail/wine-devel/2007-April/055703.html ? That one does control +relay, but I haven't figured out what's wrong with my signal handling. Thanks, Dan
On Fri, Apr 06, 2007 at 06:16:05AM -0700, Dan Kegel wrote:
nor does it help with processes that aren't listening to the keyboard.
Thanks for the input, I updated the patch. http://repo.or.cz/w/wine/hacks.git?a=commit;h=234f676e0421e073b116c2c7089677...
Can I get your opinion on my alternate patch, described at http://www.winehq.org/pipermail/wine-devel/2007-April/055703.html ? That one does control +relay, but I haven't figured out what's wrong with my signal handling.
I looked at it, but I can't find anything that seems wrong. But that doesn't mean anything because I don't have much experience with signals and I don't know how they are used in wine. I just know that it's complicated to use them correctly in wine and thus should be avoided. Perhaps there is another usable way to toggle this with applications that don't have keyboard? E.g. add some button to Wines taskmanager for this or some winelib-application that does that or use a pipe or some other means to signal this. I also read something about global keyboard shortcuts (that react on a hot-key without having focus), if wine supports those now, perhaps those can be used. With some of these it may even be possible to get this into wine. Jan
Dan Kegel a écrit :
It looks like programs/taskmgr/taskmgr used to let you edit debug channels for any process, but now that function seems broken; when I right-click on a process and select 'edit debug channels', I get column headers Debug Channel Fixme Err Warn Trace but nothing under them. Is this supposed to work? yes, but it got broken along the way I've just sent a fix for this one Note, that you can only toggle on/off debug channels that are specified on the command line when you start the program (currently you cannot add new debug channels on the fly, even if it would be doable)
A+ -- Eric Pouech "The problem with designing something completely foolproof is to underestimate the ingenuity of a complete idiot." (Douglas Adams)
participants (5)
-
Dan Kegel -
Eric Pouech -
Jan Zerebecki -
Roderick Colenbrander -
Stefan Dösinger