Skip to content

Loading…

Fails to run on windows #27

Closed
brendanjerwin opened this Issue · 10 comments

5 participants

@brendanjerwin
Guard member

Getting the following error when running in windows:

←[0mUsing polling (Please help us to support your system better than that.)←[0m
C:/Ruby192/lib/ruby/gems/1.9.1/gems/guard-0.2.2/lib/guard/interactor.rb:6:in `trap': unsupported signal SIGQUIT (ArgumentError)
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/guard-0.2.2/lib/guard/interactor.rb:6:in `init_signal_traps'
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/guard-0.2.2/lib/guard.rb:24:in `start'
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/guard-0.2.2/lib/guard/cli.rb:12:in `start'
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/thor-0.14.6/lib/thor/task.rb:22:in `run'
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/thor-0.14.6/lib/thor/invocation.rb:118:in `invoke_task'
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/thor-0.14.6/lib/thor.rb:263:in `dispatch'
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/thor-0.14.6/lib/thor/base.rb:389:in `start'
        from C:/Ruby192/lib/ruby/gems/1.9.1/gems/guard-0.2.2/bin/guard:6:in `<top (required)>'
        from C:/Ruby192/bin/guard:19:in `load'
        from C:/Ruby192/bin/guard:19:in `<main>'
@thibaudgg
Guard member

Ok Windows seems to not knowing SIGQUIT signal, do you know a list of available signals on windows?

@thibaudgg
Guard member

Still an issue for you? (Please close this issue if not)

@stereobooster

Issue for me too. Windows 7 x64

←[0mUsing polling (Please help us to support your system better than that.)←[0m
D:/tools/ruby-1.9.2-p136-i386-mingw32/lib/ruby/gems/1.9.1/gems/guard-0.3.1/lib/guard/interactor.rb:6:in `trap': unsupported signal SIGQUIT (ArgumentError)
    from D:/tools/ruby-1.9.2-p136-i386-mingw32/lib/ruby/gems/1.9.1/gems/guard-0.3.1/lib/guard/interactor.rb:6:in `init_signal_traps'
    from D:/tools/ruby-1.9.2-p136-i386-mingw32/lib/ruby/gems/1.9.1/gems/guard-0.3.1/lib/guard.rb:29:in `start'
    from D:/tools/ruby-1.9.2-p136-i386-mingw32/lib/ruby/gems/1.9.1/gems/guard-0.3.1/lib/guard/cli.rb:15:in `start'
    from D:/tools/ruby-1.9.2-p136-i386-mingw32/lib/ruby/gems/1.9.1/gems/thor-0.14.6/lib/thor/task.rb:22:in `run'
    from D:/tools/ruby-1.9.2-p136-i386-mingw32/lib/ruby/gems/1.9.1/gems/thor-0.14.6/lib/thor/invocation.rb:118:in `invoke_task'
    from D:/tools/ruby-1.9.2-p136-i386-mingw32/lib/ruby/gems/1.9.1/gems/thor-0.14.6/lib/thor.rb:263:in `dispatch'
    from D:/tools/ruby-1.9.2-p136-i386-mingw32/lib/ruby/gems/1.9.1/gems/thor-0.14.6/lib/thor/base.rb:389:in `start'
    from D:/tools/ruby-1.9.2-p136-i386-mingw32/lib/ruby/gems/1.9.1/gems/guard-0.3.1/bin/guard:6:in `<top (required)>'
    from D:/tools/ruby-1.9.2-p136-i386-mingw32/lib/ruby/gems/1.9.1/bin/guard:19:in `load'
    from D:/tools/ruby-1.9.2-p136-i386-mingw32/lib/ruby/gems/1.9.1/bin/guard:19:in `<main>'
@thibaudgg
Guard member

Do you know if there is an equivalent for "QUIT" signal on windows?
You can change it here: https://github.com/guard/guard/blob/master/lib/guard/interactor.rb
Some tips here: http://stackoverflow.com/questions/876006/how-to-trap-signal-on-ruby-running-on-windows

As I don't have a Windows machine I can't test it for you, sorry. In the meantime if other signals trapping are working (INT & TSTP) and you don't use too much "QUIT" you can just comment it.

@stereobooster

Here is the list of supported signals on my machine

{"EXIT"=>0, "INT"=>2, "ILL"=>4, "ABRT"=>22, "FPE"=>8, "KILL"=>9, "SEGV"=>11, "TERM"=>15}

I'll try to comment QUIT

@stereobooster stereobooster added a commit to stereobooster/guard that referenced this issue
@stereobooster stereobooster fix issue #27 cbe2cb3
@brandensilva

I've verified that stereobooster commit fixes this issue on my Win 7 x64 machine. Although it doesn't allow you any functionally with these keyboard shortcuts, it at least works and executes.

@thibaudgg
Guard member

Yes, trapping signals on Windows seems impossible :(. We need to found a workaround. Have you any ideas?

@thibaudgg
Guard member

Discussion about Signals trapping continues here

@thibaudgg thibaudgg closed this
@JamesMaroney

stereobooster's commit fixed this for me also on Windows. It would be awesome if this fix could be rolled into the official guard gem release.

@thibaudgg
Guard member

It's already in the master branch. You can use it right now with bundler: gem 'guard', :git => 'git://github.com/guard/guard.git'. A new gem release will comes soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.