Re: Update RelayExclude and add RelayFromExclude filter in order to avoid not useful APIs in the traces

2006-10-23 Thread Mike Hearn
On Thu, 19 Oct 2006 06:28:28 -0600, Vitaliy Margolen wrote: > Please don't. Kernel32 is the source of all core functionality. As well > as winex11drv, user32 and gdi32. No this will generate more broken bug > reports. Kernel mainly calls into ntdll these days so you see a lot of wrapper API calls

Re: Update RelayExclude and add RelayFromExclude filter in order to avoid not useful APIs in the traces

2006-10-23 Thread Francois Gouget
On Thu, 19 Oct 2006, Vitaliy Margolen wrote: [...] > Yes sorry you are correct. > > For some reason I thought it removed all relay traces from those dlls. > But it removes only traces from internal calls to those dlls. Actually your first impression was right. RelayFromExclude filters out relay

Re: Update RelayExclude and add RelayFromExclude filter in order to avoid not useful APIs in the traces

2006-10-19 Thread Vitaliy Margolen
Dmitry Timoshkov wrote: > "Vitaliy Margolen" <[EMAIL PROTECTED]> wrote: > >> Please don't. Kernel32 is the source of all core functionality. As well >> as winex11drv, user32 and gdi32. No this will generate more broken bug >> reports. > > We are using this internally in Crossover already for 3 ye

Re: Update RelayExclude and add RelayFromExclude filter in order to avoid not useful APIs in the traces

2006-10-19 Thread Dmitry Timoshkov
"Vitaliy Margolen" <[EMAIL PROTECTED]> wrote: Please don't. Kernel32 is the source of all core functionality. As well as winex11drv, user32 and gdi32. No this will generate more broken bug reports. We are using this internally in Crossover already for 3 years and, mind you, it's very helpful.

Re: Update RelayExclude and add RelayFromExclude filter in order to avoid not useful APIs in the traces

2006-10-19 Thread Vitaliy Margolen
Dmitry Timoshkov wrote: > Hello, > > please use this version intead of the previous one. > > Changelog: > Update RelayExclude and add RelayFromExclude filter in order to avoid not > useful APIs in the traces, and greatly reduce the size of the relay logs. >

Re: Default setting for RelayExclude

2005-05-31 Thread Mike Hearn
On Tue, 31 May 2005 15:08:37 +0200, Alexandre Julliard wrote: > I'm not really opposed to the idea, but your suggested defaults are > not really a good choice IMHO. Which ones would you choose? The ones in the list were based on filtering out "known bad" calls from a sample relay trace until I fel

Re: Default setting for RelayExclude

2005-05-31 Thread Alexandre Julliard
Mike Hearn <[EMAIL PROTECTED]> writes: > On Thu, 26 May 2005 01:15:45 +0100, Mike Hearn wrote: > > Mike Hearn <[EMAIL PROTECTED]> > > Default setting for RelayExclude > > Alexandre, any reason this didn't get in? I'm not really opposed to the idea, b

Re: Default setting for RelayExclude

2005-05-29 Thread Mike Hearn
On Thu, 26 May 2005 01:15:45 +0100, Mike Hearn wrote: > Mike Hearn <[EMAIL PROTECTED]> > Default setting for RelayExclude Alexandre, any reason this didn't get in? thanks -mike

Re: RelayExclude

2004-07-28 Thread Uwe Bonnes
>>>>> "Robert" == Robert Reif <[EMAIL PROTECTED]> writes: Robert> Dmitry Timoshkov wrote: >> "Diego 'Flameeyes' PettenР" <[EMAIL PROTECTED]> wrote: >> >> >> >>> I've a

Re: RelayExclude

2004-07-27 Thread Robert Reif
Dmitry Timoshkov wrote: "Diego 'Flameeyes' PettenР" <[EMAIL PROTECTED]> wrote: I've a question about RelayExclude setting in [Debug] section of ~/.wine/config : I was trying to debug the load of ClrMamePro watching at the relay output, but there's a lot of c

Re: RelayExclude

2004-07-26 Thread Dmitry Timoshkov
"Diego 'Flameeyes' PettenР" <[EMAIL PROTECTED]> wrote: > I've a question about RelayExclude setting in [Debug] section of > ~/.wine/config : > I was trying to debug the load of ClrMamePro watching at the relay output, > but there'

RelayExclude

2004-07-26 Thread Diego 'Flameeyes' Pettenò
Hi, I've a question about RelayExclude setting in [Debug] section of ~/.wine/config : I was trying to debug the load of ClrMamePro watching at the relay output, but there's a lot of call of ntdll.RtlEnterCriticalSection ntdll.RtlLeaveCriticalSection and so on. I already added them to Re