I'm seeing this behaviour in Staticmatic when I do "staticmatic
I applied the patch found on lighthouse and it fixed the issue. Someone
at the end of the thread said the problem might be related to older
mswin builds, but I'm seeing this in my mingw versions.
Thoughts, anyone? Would be good to get that patch rolled into rack if it
is an appropriate fix.
You received this message because you are subscribed to the Google Groups "RubyInstaller" group.
To post to this group, send email to rubyin...@googlegroups.com.
To unsubscribe from this group, send email to rubyinstalle...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyinstaller?hl=en.
Actually, it is helpful because the more people that come forward and
talk about it, the more attention it gets and the more likely it is to
get properly fixed. It also helps others who are suffering the same
problem and are searching for a fix.
The problem is that basically INT is not being handled properly under Windows.
mongrel_rails is quite capable of receiving the message and stopping
the server, the problem is rack and script/server and they way they
hook up or trap INT.
This has nothing to do with Visual C old or new or MinGW.
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exupéry
The patch posted on Lighthouse is taken from Mongrel. Is this the
recommended workaround? It works for me.
> This has nothing to do with Visual C old or new or MinGW.
No, I didn't think it would be, but I thought you'd be able to give a
definitive answer on it. :)
Shall I reply to those threads with this info? Shall I recommend they
apply that patch?
The trap of INT is correct, but dunno the utility/usefulness of the
The trap in the right place should be caught even when a socket is listening.
>> This has nothing to do with Visual C old or new or MinGW.
> No, I didn't think it would be, but I thought you'd be able to give a
> definitive answer on it. :)
> Shall I reply to those threads with this info? Shall I recommend they apply
> that patch?
Well, I think this should be fixed in Rack too, not just Rails. Rails
has the problem with script/server, but Rack has the problem running
with any adapter on Windows, not just mongrel.