blocks|key|3934423|text|是。kill的名字有点不对--它可以发送任何信号。kill有许多用途，它们根本不会导致进程被终止！|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3934424|entityMap^0|2|4|P|4|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

Yes. <code>kill</code> is somewhat misnamed -- it can send any signal. There are many uses for <code>kill</code> which don't result in the process being killed at all!

blocks|key|1859924|text|如果你想让一个应用程序从另一个程序中转储它的核心，几乎唯一的方法就是通过一个信号。SEGV可以很好地解决这个问题。或者，您可以将调试器挂接到程序上，然后冻结它并查看它的寄存器等，而不会终止它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1859925|如果您想从应用程序内部转储核心，有更好的方法，比如通过assert()。|1859926|所以，不，向程序发送SEGV并不是特别错误。你也可以发送像SIGILL这样的非法指令，或者一个除以零的信号。一切都很好。|1859927|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

If you want to make an application dump it's core from another program, pretty much the only way to do it is via a signal. SEGV would be fine for this. Alternatively you can hook a debugger up to the program and freeze it and view it's registers and such without killing it.

If you want to dump a core from within an application there are nicer ways to do it, like via an assert().

So, no, it's not particularly wrong to send a SEGV to a program. You could also send things like SIGILL for illegal instruction, or a divide by zero signal. It's all fine.

blocks|key|1859963|text|在Unix/Linux中这样做的方法是调用abort()，它会将SIGABORT发送到当前进程。另一个选项是raise()，您可以在其中指定要发送到当前进程的信号。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1859964|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The way to do it in Unix/Linux is to call abort() which will send SIGABORT to current process. The other option is raise() where you can specify what signal you want to send to current process.

blocks|key|2286358|text|如果您希望生成核心转储，则SIGQUIT是发送给程序的正确信号。kill是发送信号的正确命令行程序(它的名字当然不好，因为不是所有的信号都会杀死程序)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2286359|注意，您不应该向程序发送随机信号，并不是所有信号都会产生核心转储。它们中的许多将由程序本身处理，要么被消耗，要么被忽略，要么引发其他处理。因此，发送SIGSEGV是错误的。|2286360|2286361|GCC说：http://www.gnu.org/s/libc/manual/html_node/Termination-Signals.html|2286362|POSIX/Unix说：http://pubs.opengroup.org/onlinepubs/009695399/basedefs/signal.h.html|2286363|entityMap|0|LINK|mutability|MUTABLE|url|http://www.gnu.org/s/libc/manual/html_node/Termination-Signals.html|1|http://pubs.opengroup.org/onlinepubs/009695399/basedefs/signal.h.html^0|W|4|0|0|0|5|1V|0|0|C|1X|1|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|10|8|@]|D|@]|E|$]]|$1|I|3|J|5|6|7|11|8|@]|D|@$9|12|A|13|1|14]]|E|$]]|$1|K|3|L|5|6|7|15|8|@]|D|@$9|16|A|17|1|18]]|E|$]]|$1|M|3|-4|5|6|7|19|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]|U|$5|P|Q|R|E|$S|V]]]]

SIGQUIT is the correct signal to send to a program if you wish to produce a core dump. <code>kill</code> is the correct command line program to send signals (it is of course poorly named, since not all signals will kill the program).

Note, you should not send random signals to the program, not all of them will produce a core dump. Many of them will be handled by the program itself, either consumed, ignored, or induce other processing. Thus sending a SIGSEGV is wrong.

<hr>

GCC Says:
<a href="http://www.gnu.org/s/libc/manual/html_node/Termination-Signals.html" rel="noreferrer">http://www.gnu.org/s/libc/manual/html_node/Termination-Signals.html</a>

POSIX/Unix Says:
<a href="http://pubs.opengroup.org/onlinepubs/009695399/basedefs/signal.h.html" rel="noreferrer">http://pubs.opengroup.org/onlinepubs/009695399/basedefs/signal.h.html</a>

blocks|key|1860066|text|理查德·史蒂文斯(+UNIX环境中的_Advanced编程)写道：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1860067|1860068|内核的生成是大多数Unix的一个实现特性。它不是POSIX.1的一部分。|blockquote|1860069|1860070|1860071|他列出了12个信号，它们的默认操作是以核心终止(ANSI:+SIGABRT，SIGFPE，SIGILL，SIGSEGV，POSIX:+SIGQUIT，Other:+SIGBUS，SIGEMT，SIGIOT，SIGSYS，SIGTRAP，SIGXCPU，SIGXFSZ)，所有这些信号都是可重写的(两个不可重写的信号是SIGKILL和SIGSTOP)。|1860072|我从来没有看到过一种不使用默认信号处理程序来生成内核的方法。|1860073|因此，如果您的目标是生成一个核心并停止，最好的方法是选择一个默认处理程序执行此工作的信号(SIGSEGV完成此工作)，重置信号的默认处理程序(如果您正在使用它，然后使用kill+)。|1860074|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|R|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|T|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|U|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|V|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|W|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|O|$]]

Richard Stevens (_Advanced Programming in the UNIX Environment) wrote:

<blockquote>
 The generation of core is an implementation features of most Unix. It is not part of POSIX.1.
</blockquote>

He lists 12 signals whose default action is to terminate with a core (ANSI: SIGABRT, SIGFPE, SIGILL, SIGSEGV, POSIX: SIGQUIT, Other: SIGBUS, SIGEMT, SIGIOT, SIGSYS, SIGTRAP, SIGXCPU, SIGXFSZ), all of them are overwritable (the two signals which aren't overwritable are SIGKILL and SIGSTOP).

I've never seen a way to generate a core which isn't the use of a default signal handler.

So if your goal is to generate a core and stop, the best is to choose a signal whose default handler does the job (SIGSEGV does the job), reset the default handler for the signal if you are using it and then use kill.

I just came across some code which used the kill system call to send a SIGSEGV signal to an app. The rationale behind this was that this would force the app to core dump and quit. This seems so wrong to me, is this normal practice?

What is the correct way to force an app to core dump and quit?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我刚刚遇到了一些使用kill系统调用向应用程序发送SIGSEGV信号的代码。这背后的理由是，这将迫使应用程序核心转储和退出。对我来说，这似乎是错误的，这是正常的做法吗？

问强制应用程序核心转储并退出的正确方法是什么？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问强制应用程序核心转储并退出的正确方法是什么？EN