This series covers various fixes & improvements when a crash happens in a program which fires up winedbg in auto mode.
Firstly, winedbg is a bit too strict for detecting the startup sequence (and fails to display the backtrace in these stricter cases). Third patch relaxes the startup conditions in that case.
Secondly, if failing programs is a GUI, winedbg is launched in a new console (since GUI are now detached from console), but console is closed after winedbg terminates (which is after printing the crash details). So rather not useful :-(
To work around this, conhost in its configuration dialog has tab 'Configuration' / 'End of program' / 'Close console' checkbox But which is not implemented. Second patch add supports for this in conhost.
Lastly, conhost has the ability to store configuration per application. Hence, one can configure conhost with specific settings for winedbg. Interesting options are: - setting very high buffer zone so that conhost keeps track of all winedbg output, - unchecking the 'Close console' option. To set it for winedbg, - start it with './wine wineconsole winedbg' - use 'Properties' from the menu (right-click in conhost) to set the options for winedbg
Since 68f3a8e699904bd308de0da4a1e1d2c9eb91ea96, conhost doesn't pick the registry entry for winedbg (if it exists) when started with './wine wineconsole winedbg'. Third patch solves that in a somehow hacky way, but couldn't find a better option that doesn't break https://bugs.winehq.org/show_bug.cgi?id=10941
-- v3: winedbg: No longer expect a startup sequence in auto mode. conhost: Support the close-on-exit configuration option. wineconsole: Ensure conhost gets the expected title.