-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows build doesn't exit cleanly when terminated externaly #2
Comments
Submitted b68b0e3, thank you. |
Should reopen. The patch was applied incorrectly (and cleanup indeed isn't performed). The WM_CLOSE case should be at the same level as the WM_USER case, not inside it (it's msg, not lParam). |
Ouch, facepalm. Sorry, I wasn't attentive enough. Pushed 0c5c3b1, please verify. |
Yeah, that works, thanks :) Also, I hope it's OK to ask here about compilation:
Thanks in advance for your replies, and for mongoose itself :) |
|
OK, thank for the quick replies. For future reference, here's the output of 'make mingw' on my system: |
…lete (mg_read() --> 0); also enlarge the tail header set for the chunked transfer I/O tests in an attempt to increase the chances to trigger edge case cesanta#2 (buffer overflow detect while fetching tail headers)
Just wanted to note that with the WM_CLOSE issue fixed, I've included mongoose in portable-quassel-backlog-search here: http://bugs.quassel-irc.org/projects/1/wiki/Quassel_Logging#Windows-Portable-quasselsuche . Thanks again :) |
Cool, thank you! On Sun, Aug 19, 2012 at 6:14 PM, avih notifications@github.com wrote:
|
When using taskkill or sending the WM_CLOSE message:
Here's a patch which fixes both issues:
The text was updated successfully, but these errors were encountered: