On Sat, May 8, 2010 at 11:09, Timothy Brownawell wrote:
> On 05/03/2010 01:29 PM, Daniel Atallah wrote:
>>
>> Initially, it looked like this was working nicely and the annoying
>> crash message no longer appeared when Ctrl+C was issued.
>>
>> However, it looks like the fix for this has an (at leas
On 05/03/2010 01:29 PM, Daniel Atallah wrote:
Initially, it looked like this was working nicely and the annoying
crash message no longer appeared when Ctrl+C was issued.
However, it looks like the fix for this has an (at least in my view)
undesirable side effect.
I frequently run something like
On Thu, Mar 4, 2010 at 09:51, Timothy Brownawell wrote:
> Timothy Brownawell wrote:
>>
>> Hm, maybe calling TerminateProcess() would be the better choice. The
>> warning is "The state of global data maintained by dynamic-link libraries
>> (DLLs) may be compromised if TerminateProcess is used rathe
Timothy Brownawell wrote:
Hm, maybe calling TerminateProcess() would be the better choice. The
warning is "The state of global data maintained by dynamic-link
libraries (DLLs) may be compromised if TerminateProcess is used rather
than ExitProcess.", and since none of our shared libraries are fo
J Decker wrote:
ExitProcess invokes things like static class destructors, and atexit()
registered code. Terminate process ends the process immediately.
Probably the default break handler calls ExitProcess... and don't you
mean a break handler that returns TRUE so it doesn't segfault?
The issue
ExitProcess invokes things like static class destructors, and atexit()
registered code. Terminate process ends the process immediately.
Probably the default break handler calls ExitProcess... and don't you
mean a break handler that returns TRUE so it doesn't segfault?
On Tue, Mar 2, 2010 at 12:43
Way back in October, Timothy Brownawell wrote:
J Decker wrote:
When I abort an operation in monotone for windows, an exception is
generated. I have tolerated this since version 0.26... but... no I'm
tried of having to wait for the exception handler to log the
exception... y'all should implement
J Decker wrote:
> When I abort an operation in monotone for windows, an exception is
> generated. I have tolerated this since version 0.26... but... no I'm
> tried of having to wait for the exception handler to log the
> exception... y'all should implement
>
> SetConsoleCtrlHandler
>
> and handl
When I abort an operation in monotone for windows, an exception is
generated. I have tolerated this since version 0.26... but... no I'm
tried of having to wait for the exception handler to log the
exception... y'all should implement
SetConsoleCtrlHandler
and handle exiting nicely instead of blow
