blocks|key|2323324|text|C%2B%2B标准本身并不关心seg-错误(这是特定于平台的事情)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2323325|实际上，这取决于您做什么，以及您对“内存泄漏”的定义是什么。理论上，您可以为seg-故障信号注册一个处理程序，在该处理程序中您可以进行所有必要的清理。然而，任何现代操作系统都会自动清除终止进程。|2323326|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

The C++ standard does not concern itself with seg-faults (that's a platform-specific thing).

In practice, it really depends on what you do, and what your definition of "memory leak" is. In theory, you can register a handler for the seg-fault signal, in which you can do all necessary cleanup. However, any modern OS will automatically clear up a terminating process anyway.

blocks|key|3204336|text|在发生seg故障时，操作系统负责清理程序所持有的所有资源。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3204337|编辑：|3204338|无论程序是如何终止的，现代操作系统都会清理任何泄漏的内存。内存仅在程序的生命周期内泄漏。大多数操作系统还将清理许多其他类型的资源，如打开的文件和套接字连接。|3204339|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|$]]

In the event of a seg fault, the OS is responsible for cleaning up all the resources held by your program.

Edit:

Modern operating systems will clean up any leaked memory regardless of how your program terminates. The memory is only leaked for the life of your program. Most OS's will also clean up many other types of resources such as open files and socket connections.

blocks|key|2346082|text|第一，系统负责清理资源。其中之一就是记忆。您不必担心在分段错误上永久泄漏RAM。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2346083|第二，有些资源是系统不负责清理的。您可以编写一个程序，将其pid插入数据库并在关闭时删除它。不会在断层上被移除的。您可以添加一个处理程序来清理这类非系统资源，也可以修复程序中的bug。|2346084|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

One, there are resources the system is responsible for cleaning up. One of them is memory. You do not have to worry about permanently leaked RAM on a segfault.

Two, there are resources that the system is not responsible for cleaning up. You could write a program that inserts its pid into a database and removes it on close. That won't be removed on a segfault. You can either 1) add a handler to clean up that sort of non-system resources, or 2) fix the bugs in your program to begin with.

blocks|key|3204470|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3204471|是否有可能，如果在分配内存之后发生分段错误，但在释放它之前，会泄漏内存(也就是说，内存永远不会被释放，从而导致内存泄漏)吗？|blockquote|3204472|3204473|3204474|是的和不是的:崩溃的过程应该完全由操作系统来处理。但是，请考虑由您的流程生成的其他进程:它们可能不会完全终止。然而，通常这些应该不会占用太多的资源，但这可能会因您的程序而有所不同。请参阅http://en.wikipedia.org/wiki/Zombie_process|offset|length|3204475|如果是的话，是否有任何方法确保在发生分段错误时清除分配的内存？|3204476|3204477|如果程序是非关键的(这意味着如果它崩溃就没有生命危险)，我建议修复分段错误。如果您真的需要能够处理分段错误，请参阅本主题的答案：How+to+catch+segmentation+fault+in+Linux?|3204478|UPDATE：请注意，尽管可以处理SIGSEGV信号(并保持程序流)，但这并不是一种安全的依赖方式，因为--正如下面的注释所指出的--它是未定义的行为，意味着不同的平台/编译器/.可能有不同的反应。|style|BOLD|3204479|因此，通过任何可能的方法，修复分段错误(以及windows上的访问冲突)都应该具有第一优先级。仍然使用建议的解决方案来以这种方式处理信号，必须进行彻底的测试，如果将其放入生产代码中，您必须意识到这一点，并得出任何结果--这些结果可能会根据您的需求而变化和依赖，因此我不会给出任何结果。|3204480|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Zombie_process|1|https://stackoverflow.com/questions/2350489/how-to-catch-segmentation-fault-in-linux^0|0|0|0|0|2L|17|0|0|0|0|1S|15|1|0|0|6|0|0^^$0|@$1|2|3|-4|4|5|6|14|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|15|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|16|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|17|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|18|7|@]|8|@$H|19|I|1A|1|1B]]|9|$]]|$1|J|3|K|4|5|6|1C|7|@]|8|@]|9|$]]|$1|L|3|-4|4|5|6|1D|7|@]|8|@]|9|$]]|$1|M|3|N|4|5|6|1E|7|@]|8|@$H|1F|I|1G|1|1H]]|9|$]]|$1|O|3|P|4|5|6|1I|7|@$H|1J|I|1K|Q|R]]|8|@]|9|$]]|$1|S|3|T|4|5|6|1L|7|@]|8|@]|9|$]]|$1|U|3|-4|4|5|6|1M|7|@]|8|@]|9|$]]]|V|$W|$4|X|Y|Z|9|$10|11]]|12|$4|X|Y|Z|9|$10|13]]]]

<blockquote>
 Is it possible that, if a segfault occurs after allocating memory but
 before freeing it, this leaks memory (that is, the memory is never
 freed resulting in a memory leak)?
</blockquote>

Yes and No: The process which crashes should be tiedied completely by the OS. However consider other processes spawned by your process: They might not get terminated completely. However usually these shouldn't take too many resources at all, but this may vary depending on your program. See <a href="http://en.wikipedia.org/wiki/Zombie_process" rel="nofollow noreferrer">http://en.wikipedia.org/wiki/Zombie_process</a>

<blockquote>
 If so, is there any way to ensure allocated memory is cleaned up in
 the event of a segfault?
</blockquote>

In case the program is non critical (meaning there are no lives at stake if it crashes) I suggest fixing the segmentation fault. If you really need to be able to handle segmentation faults see the answer on this topic: <a href="https://stackoverflow.com/questions/2350489/how-to-catch-segmentation-fault-in-linux">How to catch segmentation fault in Linux?</a>

UPDATE: Please note that despite the fact that it is possible to handle SIGSEGV signals (and continuning in program flow) it is not a secure way to rely on, since - as pointed out in the comments below - it is undefined behaviour meaning differen platforms/compilers/... may react differently.

So by any means possible fixing segmentation faults (as well as access violations on windows) should have first priority. Still using the suggested solution to handle signals this way must be thoroughly tested and if put in production code you must be aware of it and draw any consequences - which may vary and depend on your requirements so I will not name any.

blocks|key|2323528|text|现代操作系统将应用程序的内存分开，以便能够清除它们之后的内存。分割错误的问题是它们通常只有在出了问题时才会发生。此时，默认行为是关闭应用程序，因为它不再像预期的那样工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2323529|同样，除非在某些奇怪的情况下，如果应用程序遇到了分段错误，您的应用程序可能会做一些无法解释的事情。因此，“清理”可能实际上是不可能的。仔细使用类似于事务性数据库的内存以保证可接受的回滚状态并不是不可能的，但是这样做(以及取决于级别的细粒度)可能超出了乏味的范围。|2323530|更实用的版本可能是在应用程序组件之间提供您自己的沙箱，并在组件死后重新启动组件，将其还原到以前保存的可接受状态。这样，您就可以刷新它分配的所有内存，并让它从头开始。但是，您仍然丢失了它在上一个检查点时没有保存的数据。|2323531|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|$]]

Modern operating systems separate applications' memory as to be able to clean up after them. The problem with segmentation faults is that they normally only occur when something goes wrong. At this point, the default behavior is to shut down the application because it's no longer functioning as expected.

Likewise, unless under some bizarre circumstance, your application has likely done something you cannot account for if it has hit a segmentation fault. So, "cleaning up" is likely practically impossible. It's not out of the realm of possibility to use memory carefully similar to transactional databases in order to guarantee an acceptable roll-back state, however doing so (and depending on how fine-grained of a level) may be beyond tedious.

A more practical version may be to provide your own sort of sandboxing between application components and reboot a component if it dies, restoring it to a acceptable previous saved state wholesale. That way you can flush all of its allocated memory and have it start from scratch. You still lose whatever data it hadn't saved as of the last checkpoint, however.

My question has two parts:

<ul>
<li>Is it possible that, if a segfault occurs after allocating memory but before freeing it, this leaks memory (that is, the memory is never freed resulting in a memory leak)? </li>
<li>If so, is there any way to ensure allocated memory is cleaned up in the event of a segfault?</li>
</ul>

I've been reading about memory manamgement in C++ but was unable to find anything about my specific question.

Segfaults and Memory leaks

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我的问题有两部分：是否有可能，如果在分配内存之后发生分段错误，但在释放该错误之前，这会泄漏内存(也就是说，内存从未被释放导致内存泄漏)？，如果是这样的话，有没有办法确保在发生分段错误时清除分配的内存？我在C++上读过关于记忆管理的文章，但是没有找到任何关于我的具体问题的东西。

问分段故障与内存泄漏
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问分段故障与内存泄漏EN