| commit | 0ca61a24f1565ed3cbf84690d16248c4111d9d11 | |
| author | Karsten Blees <blees@dcon.de> | |
| Thu, 15 Mar 2012 13:45:49 +0000 (15 14:45 +0100) | ||
| committer | Johannes Schindelin <johannes.schindelin@gmx.de> | |
| Thu, 10 Apr 2014 18:52:15 +0000 (10 13:52 -0500) | ||
| tree | 903c33f2faebe841a04b60653d8e9e9d4565b809 | treesnapshot (tar.gz zip) |
| parent | 8e82e2a33ee8e3eceae4c7974eb0a3838a260a82 | commitdiff |
Win32: fix segfault in WriteConsoleW when debugging in gdb
On Windows XP (not Win7), WriteConsoleW and WriteFile seem to raise and
catch SIGSEGV if the lpNumberOfCharsWritten parameter is NULL. This is not
a problem when executed standalone, but gdb stops execution here (unless
disabled via "handle SIGSEGV nostop").
Fix it by passing a dummy variable.
Signed-off-by: Karsten Blees <blees@dcon.de>
On Windows XP (not Win7), WriteConsoleW and WriteFile seem to raise and
catch SIGSEGV if the lpNumberOfCharsWritten parameter is NULL. This is not
a problem when executed standalone, but gdb stops execution here (unless
disabled via "handle SIGSEGV nostop").
Fix it by passing a dummy variable.
Signed-off-by: Karsten Blees <blees@dcon.de>
| compat/winansi.c | diffblobblamehistory |