Repeated: Breakage in -relay and -snoop
Hallo, since last week, e.g a commandline like "wine <xxx> --debugmsg -relay=RtlEnterCriticalSection" inhibits _any_ relay message to be logged. Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
--- Uwe Bonnes <bon(a)elektron.ikp.physik.tu-darmstadt.de> wrote:
since last week, e.g a commandline like "wine <xxx> --debugmsg -relay=RtlEnterCriticalSection" inhibits _any_ relay message to be logged.
Great! It would be convenient to have this option on by default. So we do not have to tell ppl to use this option before they send logs to us. For precation we can show status of the debugging options in the beginning of the debugging output. What do you think? Andriy __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com
Uwe Bonnes <bon(a)elektron.ikp.physik.tu-darmstadt.de> writes:
since last week, e.g a commandline like "wine <xxx> --debugmsg -relay=RtlEnterCriticalSection" inhibits _any_ relay message to be logged.
Specifying relay functions on the command-line is no longer supported. You have to put them in the config file. -- Alexandre Julliard julliard(a)winehq.com
"Alexandre" == Alexandre Julliard <julliard(a)winehq.com> writes:
Alexandre> Uwe Bonnes <bon(a)elektron.ikp.physik.tu-darmstadt.de> writes: >> since last week, e.g a commandline like "wine <xxx> --debugmsg >> -relay=RtlEnterCriticalSection" inhibits _any_ relay message to be >> logged. Alexandre> Specifying relay functions on the command-line is no longer Alexandre> supported. You have to put them in the config file. Did I miss some announcement :-) B.t.w. what is the reason about all those commandline options vanishing into the config file? It makes changes inflexible at least... Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
Uwe Bonnes <bon(a)elektron.ikp.physik.tu-darmstadt.de> writes:
Did I miss some announcement :-)
There was a patch on wine-cvs ;-)
B.t.w. what is the reason about all those commandline options vanishing into the config file? It makes changes inflexible at least...
The basic reason is modularity; centralized option handling is incompatible with dll separation. Also command-line parsing is policy that belongs in the higher layers, we must not have kernel dictate applications what their command-line looks like. For instance today you cannot pass options to a Winelib app without using '--' first to isolate the Wine options and this is wrong. It would be perfectly possible to write a high-level wrapper to Wine to handle all sorts of options; all we need is someone to implement it... -- Alexandre Julliard julliard(a)winehq.com
participants (3)
-
Alexandre Julliard -
Andriy Palamarchuk -
Uwe Bonnes