http://bugs.winehq.org/show_bug.cgi?id=16862
Julien Valroff julien@kirya.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |julliard@winehq.org
--- Comment #7 from Julien Valroff julien@kirya.net 2009-01-25 05:00:50 --- Hi,
After some hours of testing, following the regression test procedure, I was not able to make the application run without the whole session crashes. However, I confirm that using 1.1.12, the app crashes, but not the session.
Here is the last result, which seems to however fit with the problem: $ git bisect bad 9087e5c55f35e091c5cb9ba381e0a5020d1fc0ad is first bad commit commit 9087e5c55f35e091c5cb9ba381e0a5020d1fc0ad Author: Alexandre Julliard julliard@winehq.org Date: Fri Jan 2 20:00:54 2009 +0100
server: Avoid crash on initialization of the thread creation debug event.
:040000 040000 8c296659cd98c18d8aac56e4c5605f6c873b1bef 9c9eeab986d8bcb1487556081366883defcc7020 M server
If this patch is the "bad" commit, it shows that the debugger makes the user session freeze, and not the incompatibility with the application I try to run. I am not used in doing such things, but it is true that with 1.1.12, I had no debug information (only an error message).
However, even 1.1.12 doesn't allow full use of the application.
I hope this helps!
Cheers, Julien