Skip to content
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

Does not seem to work w/o reporting any error #6

Open
gubenkoved opened this issue Jun 10, 2020 · 1 comment
Open

Does not seem to work w/o reporting any error #6

gubenkoved opened this issue Jun 10, 2020 · 1 comment

Comments

@gubenkoved
Copy link

gubenkoved commented Jun 10, 2020

I have a Console application which is correctly terminated via SendSignal original application, however, it does not work with "windows-kill" which I've installed via Chocolatey (version of package is 1.1.4 as of now) and it does not produce any error output.

image

> windows-kill -1 42128
Windows Kill 1.1.4 | Windows Kill Library 3.1.3
OS Name:                   Microsoft Windows 10 Pro
OS Version:                10.0.18363 N/A Build 18363
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
@countzero
Copy link

I can also reproduce this behaviour when installing windows-kill via Chocolatey.

But when I use the binary directly from the windows-kill_x64_1.1.4_lib_release.zip it works flawlessly:

.\windows-kill_x64_1.1.4_lib_release\windows-kill.exe -SIGINT 16312
Windows Kill 1.1.4 | Windows Kill Library 3.1.3
Signal sent successfuly. type: 0 | pid: 16312

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants