Re: [PATCH 2/3] dmsynth: Check the rigth CLSID to create the DirectMusicSynthSink object. (resend)

2012-04-21 Thread Marvin
Hi,

While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=17990

Your paranoid android.


=== WINEBUILD (build) ===
Patch failed to apply




Re: winedbg and program stdout

2012-04-21 Thread Eric Pouech

Le 21/04/2012 10:33, Ilya Basin a écrit :

When I debug a program with winedbg, it's output never goes to the
same terminal. If it's compiled with -mconsole, it goes to a new
console window; if compiled with -mwindows, the output is discarded.
Any way to change this behavior?




if your debuggee is a CUI (compiled with -m console), then winedbg 
forces to have two consoles, one for winedbg, the other one for the 
debuggee program
that's a decision. if you want to change this, remove the 
CREATE_NEW_CONSOLE flag in programs/winedbg/tgt_active.c
(actually we could make this an optional behavior of winedbg to share 
the current console with debuggee's output)


if your debuggee is a GUI, it's windows default behavior not to create 
automatically a console for this program
you need to call AllocConsole() in your debuggee for that. and it that 
case, wine will likely have to create a new window for the console


A+

--
Eric Pouech
"The problem with designing something completely foolproof is to underestimate the 
ingenuity of a complete idiot." (Douglas Adams)





winedbg and program stdout

2012-04-21 Thread Ilya Basin
When I debug a program with winedbg, it's output never goes to the
same terminal. If it's compiled with -mconsole, it goes to a new
console window; if compiled with -mwindows, the output is discarded.
Any way to change this behavior?