[bug #51237] Deadlock in Ctrl-C handler on Windows

[Paul D. Smith]

Follow-up Comment #4, bug #51237 (project make):

I would prefer this to be done differently.  Sorry for the late conversation.

First, we have this same type of issue in UNIX (see for example bug #50557) so
I would prefer to not have a Windows-specific solution.

Second, I don't see why we need a separate thread to handle this.  Why can't
we just modify the signal handler to set a flag saying that a fatal signal was
received, then test that flag in appropriate places during the main processing
of make.  If the flag is set then we die.  Of course, finding the "appropriate
places" is the trick.

Maybe there's something about Windows that makes this less straightforward
than on POSIX systems?

Finally, this implementation adds a lot more ifdefs to the code.  I'm (more
slowly than I'd like) trying to remove ifdefs by moving system-specific code
into system-specific source files and creating generic interfaces.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?51237>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/