Eric,
When running a program with "r" in winedbg, I get: fixme:winedbg:dbg_run_debuggee Re-running current program with "\r" as args is broken
Does this have anything to do with the EOL conversion issues?
J. Leclanche
On Wed, Sep 8, 2010 at 9:32 PM, Reece Dunn msclrhd@googlemail.com wrote:
On 8 September 2010 21:04, Eric Pouech eric.pouech@orange.fr wrote:
does the attached patch help with some of the concerns ? I/ it should allow typing in the console (for all GUI programs) and still see output get buffer when the programs exits II/ reduce the number of cases where the console is in raw mode after wine exits Not all the cases are supposed to be fixed. For example, this is one example of what still doesn't work
but in this case, the first program is killed at the same time as winedbg exits, which shouldn't the case) what shall remain not fixed is the case where:
- pgm A is started from shell command line
- pgm A spawns child B
- B is a CUI and tries to interact with the console by reading the input
- A dies
I still sometimes see it when exiting winedbg after it has been launched upon a fault in a running program... but, something goes wrong here as quitting winedbg (B) shouldn't kill the program beeing debugged (A)
what's not yet fixed :
- regression in EOF management
This fixes the issue with StarCraft 2.
Thanks for looking into this,
- Reece