blocks|key|184487|text|您还可以使用j控制台查看所有正在运行的线程的堆栈跟踪。这将适用于Windows和任何其他支持Java的操作系统。jconsole还有许多其他不错的特性，内存图、cpu图等等。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|184488|它没有回答你最初的问题，但希望能让你得到同样的结果。|184489|如果您不熟悉j控制台，请查看使用JConsole文档。|offset|length|184490|entityMap|0|LINK|mutability|MUTABLE|url|http://java.sun.com/javase/6/docs/technotes/guides/management/jconsole.html^0|0|0|E|A|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

You can also use jconsole to view the stacktrace of all the running threads. This will work on Windows, and any other OS that supports Java. jconsole also has many other nice features, memory graphs, cpu graphs, etc. 

It doesn't answer your original question, but hopefully allows you to get the same results.

If your not familiar with jconsole, check out the <a href="http://java.sun.com/javase/6/docs/technotes/guides/management/jconsole.html" rel="nofollow noreferrer">Using JConsole</a> documentation.

blocks|key|184501|text|我只是想知道现在微软拥有的PsTools是否会帮助你。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|184502|entityMap|0|LINK|mutability|MUTABLE|url|http://technet.microsoft.com/en-us/sysinternals/bb896649.aspx^0|D|7|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I'm just wondering if the <a href="http://technet.microsoft.com/en-us/sysinternals/bb896649.aspx" rel="nofollow noreferrer">PsTools</a> from, now Microsoft owned, <a href="http://technet.microsoft.com/en-us/sysinternals/default.aspx" rel="nofollow noreferrer">SysInternals</a> would help you.

blocks|key|184551|text|Windows不是POSIX。它没有信号。控制台程序获得的唯一“信号”是当它们调用SetConsoleCtrlHandler时，在这种情况下，可以通知用户用户已按下Ctrl%2BC、Ctrl%2BBreak、关闭控制台窗口、注销或关闭系统。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|184552|其他一切都是用IPC完成的，通常是使用窗口消息或RPC。查看Sun的文档，看看是否有一种方法可以满足您在Windows上的要求。|184553|entityMap^0|15|L|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

Windows is not POSIX. It does not have signals. The only 'signals' that console programs get is if they call <code>SetConsoleCtrlHandler</code>, in which case it can be notified that the user has pressed Ctrl+C, Ctrl+Break, closed the console window, logged off, or shut the system down.

Everything else is done with IPC, typically with window messages or RPC. Check Sun's documentation to see if there's a way to do what you're asking on the Windows JRE.

blocks|key|859010|text|在Windows中，一切都围绕着Win32消息。我不认为有命令行工具可以这样做，但在C%2B%2B中，您可以使用FindWindow向另一个Windows程序发送任意消息。例如：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|859011|#define+WM_MYMSG++(+WM_USER%2B0x100+)
HWND+h+=+::FindWindow(NULL,_T("Win32App"));
if+(h)+{
++++::PostMessage(h,+WM_MYMSG,+0,+0);
}|code-block|syntax|javascript|859012|这也可以在C#中使用com互操作来完成。|859013|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/ms633499.aspx^0|1G|A|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|C|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

In Windows everything revolves around Win32 messages. I do not believe there is a command line tool to do this, but in C++ you could use <a href="http://msdn.microsoft.com/en-us/library/ms633499.aspx" rel="nofollow noreferrer">FindWindow</a> to send an arbitrary message to another Windows program. e.g.:

<pre><code>#define WM_MYMSG ( WM_USER+0x100 )
HWND h = ::FindWindow(NULL,_T("Win32App"));
if (h) {
 ::PostMessage(h, WM_MYMSG, 0, 0);
}
</code></pre>

This can also be done in C# using com interop.

blocks|key|854854|text|如果您想要显式/以编程方式杀死任何类型的另一个程序/进程，那么在SysInternals的pstools中有一个名为"pskill“的小工具，它的行为就像Unixen的”杀死“一样。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|854855|如果你想要别的东西，继续读下去(尽管我在下面的一些细节上可能错了--自从我最后一次用C语言开发一个Windows程序以来，我一直只使用WinAPI和Charles的优秀书籍“为Windows编程”作为指南)。|854856|在Windows上，没有正确的“信号”，WinMain和WinProc从操作系统接收的功能都是简单的消息。例如，当您单击窗口的"X“按钮时，Windows会向该窗口的处理程序发送消息WM_CLOSE。当窗口被删除但程序仍在运行时，它会发送WM_DESTROY。当它即将退出主消息处理循环时，WinMain+(而不是WinProc)接收WM_QUIT。您的程序应该像预期的那样响应所有这些--您实际上可以开发一个“不可关闭”的应用程序，在接收到WM_CLOSE时不做它应该做的事情。|854857|当用户从中选择任务并单击"End“时，操作系统将发送WM_CLOSE+(以及另一个我不记得的任务)。但是，如果使用"End+Process"，则进程将直接终止，不会发送任何消息(源：旧的新事物)。|offset|length|854858|我记得有一种方法可以获得另一个进程窗口的HWND，一旦您得到该窗口，另一个进程就可以通过PostMessage和DispatchMessage函数发送消息。|854859|entityMap|0|LINK|mutability|MUTABLE|url|https://devblogs.microsoft.com/oldnewthing/20040722-00/?p=38373^0|0|0|0|2J|5|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$H|X|I|Y|1|Z]]|A|$]]|$1|J|3|K|5|6|7|10|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]]]

If what you want is to explicitly/programmatically kill another program/process of any kind, within the SysInternals' pstools there is a small tool named &quot;pskill&quot; that behaves just like Unixen &quot;kill&quot; would do.
If you want something else, keep reading (though I may be wrong on some of the specifics below - it's been eons since I last developed a Windows program in C using only the WinAPI and Charles Petzold's excellent books &quot;Programming for Windows&quot; as a guide).
On Windows you don't properly have &quot;signals&quot;, what functions WinMain and WinProc receive from the Operating System are simple messages. For instance, when you click on the &quot;X&quot; button of a window, Windows sends that windows' handler the message WM_CLOSE. When the window's deleted but program's still running, it sends WM_DESTROY. When it's about to get out of the main message processing loop, WinMain (not WinProc) receives WM_QUIT. Your program should respond to all these as expected - you can actually develop an &quot;unclosable&quot; application by not doing what it should upon receiving a WM_CLOSE.
When user selects the task from Windows Task Manager and clicks &quot;End Task&quot;, the OS will send WM_CLOSE (and another one I don't remember). If you use &quot;End Process&quot;, though, the process is killed directly, no messages sent ever (source: <a href="https://devblogs.microsoft.com/oldnewthing/20040722-00/?p=38373" rel="nofollow noreferrer">The Old New Thing</a>)
I remember there was a way to get the HWND of another process' window, once you get that another process could send that window a message thru functions PostMessage and DispatchMessage.

blocks|key|184646|text|Ruby可以在windows上(至少模仿)+SIGINT+SIGKILL等，并捕获这些消息。可能想去看看。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|184647|在windows下，ruby是如何“发送信号SIGINT到该进程”的，实际上是调用TerminateProcess或该PID上的等效值。|offset|length|style|CODE|184648|还有一种与windows等效的“捕获ctrl%2Bc”方法--我想这就是它所称的。|184649|entityMap^0|0|15|G|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

Ruby is somehow able to (at least emulate) SIGINT SIGKILL etc. on windows, and trap those messages. Might want to check it out.

How ruby does "send signal SIGINT to that process" underneath, in windows, is actually to call <code>TerminateProcess</code> or equivalent on that PID.

There's also a windows equivalent method for "catching ctrl+c" I imagine it's what it calls there.

blocks|key|1183601|text|SIGINT和其他信号可以被发送到使用杀窗+(以前是在这里在原始作者的GitHub上，但现在消失了，也多亏了@NathanOsman我们有web档案的源或二进制版本的web档案+)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1183602|通过语法windows-kill+-SIGINT+PID使用，其中PID可以由微软的银屑病单获得。|style|CODE|1183603|关于捕获SIGINTs，如果您的程序是使用Python的，那么您可以像在这个解决方案中那样实现SIGINT处理/捕获。|1183604|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/ElyDotDev/windows-kill/releases|1|https://github.com/alirdn/windows-kill/releases|2|https://web.archive.org/web/20200910171157if_/https://codeload.github.com/alirdn/windows-kill/tar.gz/1.1.4|3|https://web.archive.org/web/20201111213611/https://github.com/alirdn/windows-kill/releases|4|https://download.sysinternals.com/files/PSTools.zip|5|https://stackoverflow.com/a/31464349/941531^0|J|2|0|Q|3|1|1X|5|2|2B|5|3|0|4|O|X|3|16|4|4|0|10|6|5|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@$A|12|B|13|1|14]|$A|15|B|16|1|17]|$A|18|B|19|1|1A]|$A|1B|B|1C|1|1D]]|C|$]]|$1|D|3|E|5|6|7|1E|8|@$A|1F|B|1G|F|G]|$A|1H|B|1I|F|G]]|9|@$A|1J|B|1K|1|1L]]|C|$]]|$1|H|3|I|5|6|7|1M|8|@]|9|@$A|1N|B|1O|1|1P]]|C|$]]|$1|J|3|-4|5|6|7|1Q|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]|R|$5|M|N|O|C|$P|S]]|T|$5|M|N|O|C|$P|U]]|V|$5|M|N|O|C|$P|W]]|X|$5|M|N|O|C|$P|Y]]|Z|$5|M|N|O|C|$P|10]]]]

SIGINT and other signals can be send to program using <a href="https://github.com/ElyDotDev/windows-kill/releases" rel="nofollow noreferrer">windows-kill</a> (previously <a href="https://github.com/alirdn/windows-kill/releases" rel="nofollow noreferrer">was here</a> on original author's GitHub, but now disappeared, also thanks to @NathanOsman we have <a href="https://web.archive.org/web/20200910171157if_/https://codeload.github.com/alirdn/windows-kill/tar.gz/1.1.4" rel="nofollow noreferrer">web archive</a> of sources or <a href="https://web.archive.org/web/20201111213611/https://github.com/alirdn/windows-kill/releases" rel="nofollow noreferrer">web archive</a> of binary releases).
Using by syntax <code>windows-kill -SIGINT PID</code>, where <code>PID</code> can be obtained by Microsoft's <a href="https://download.sysinternals.com/files/PSTools.zip" rel="nofollow noreferrer">pslist</a>.
Regarding catching SIGINTs, if your program is in Python then you can implement SIGINT processing/catching like in <a href="https://stackoverflow.com/a/31464349/941531">this solution</a>.

Linux supports sending an arbitrary Posix-Signal such as <code>SIGINT</code> or <code>SIGTERM</code> to a process using the <code>kill</code>-Command. While <code>SIGINT</code> and <code>SIGTERM</code> are just boring old ways to end a process in a friendly or not-so-friendly kind of way, <code>SIGQUIT</code> is meant to trigger a core dump. This can be used to trigger a running Java VM to print out a thread dump, including the stacktraces of all running threads -- neat! After printing the debugging info, the Java VM will continue doing whatever it was doing before; in fact the thread dump just happens in another spawned thread of maximum priority. (You can try this out yourself by using <code>kill -3 &lt;VM-PID&gt;</code>.)

Note that you can also register your own signal handlers using the (unsupported!) <code>Signal</code> and <code>SignalHandler</code> classes in the <code>sun.misc</code>-package, so you can have all kinds of fun with it.

However, I have yet to find a way to send a signal to a Windows process. Signals are created by certain user inputs: <code>Ctrl-C</code> triggers a <code>SIGINT</code> on both platforms, for instance. But there does not seem to be any utility to manually send a signal to a running, but non-interactive process on Windows. The obvious solution is to use the Cygwin <code>kill</code> executable, but while it can end Windows processes using the appropriate Windows API, I could not send a <code>SIGBREAK</code> (the Windows equivalent to <code>SIGQUIT</code>) with it; in fact I think the only signal it is able to send to Windows processes is <code>SIGTERM</code>.

So, to make a long story short and to repeat the headline: How to I send an arbitrary signal to a process in Windows?

Sending an arbitrary Signal in Windows?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

Linux支持将任意Posix信号(如SIGINT或SIGTERM )发送到使用kill-Command的进程。虽然SIGINT和SIGTERM只是以友好或不友好的方式结束进程的无聊的老方法，但SIGQUIT是用来触发核心转储的。这可以用来触发运行中的Java来打印出线程转储，包括所有正在运行的线程的堆栈-整齐！打印调...

问在Windows中发送任意信号？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Windows中发送任意信号？EN