blocks|key|2557564|text|我相信你要找的是这个：How+to+generate+a+stacktrace+when+my+gcc+C%2B%2B+app+crashes|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2557565|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/77005/how-to-generate-a-stacktrace-when-my-gcc-c-app-crashes^0|B|1K|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 believe what you're looking for is this: <a href="https://stackoverflow.com/questions/77005/how-to-generate-a-stacktrace-when-my-gcc-c-app-crashes">How to generate a stacktrace when my gcc C++ app crashes</a>

blocks|key|3965736|text|如果磁盘上有空间，让应用程序在崩溃时创建其核心转储。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3965737|ulimit+-c+unlimited|code-block|syntax|javascript|3965738|稍后您可以使用GDB对其进行调试。|3965739|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

If you have space on the disk, let the application create its coredump when it crashes.

<pre><code>ulimit -c unlimited
</code></pre>

Later you can debug it with GDB.

blocks|key|795001|text|除了已经提到的核心转储和堆栈跟踪之外-确保您可以轻松地识别您的可执行文件的哪些版本正在运行，并且能够回答每个源文件的哪个版本进入哪个二进制版本(例如，花一些时间在您的源代码控制系统和构建脚本上)。否则，核心文件和堆栈跟踪都无济于事。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|795002|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|$]]

Aside from coredumping and stacktracing as already noted - make sure you can easily identify which versions of your executable people are running, and be able to answer what version of each source file goes into what binary version (i.e. spend some time with your source code control system and your build scripts). Otherwise neither a core file nor a stack trace is going to help.

blocks|key|797071|text|核心转储是有帮助的，但它们并不总是告诉您您想知道的关于错误条件下的最终结果的所有信息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|797072|记录操作、输入和事件可能非常有用。如果您能够以这样一种方式记录程序的每次运行，即在发生崩溃时，开发人员可以访问日志并重新生成错误，这将非常有帮助。|797073|如果可能，你应该使用生成的最大调试符号来构建你的程序，如果你不想或不能让你的发布版本拥有它们，那么就去掉它们，但是保留一个带有调试符号的每个发布版本的副本，如果你需要调试崩溃，你可以与核心文件耦合。|797074|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|$]]

Core dumps are helpful, but they don't always tell you everything you want to know about how you ended up in the error condition.

Logging actions, inputs, and events can be very helpful. If you are able to log each run of your program in such a way that in the event of a crash a developer could get access to the log and regenerate the error could be very helpful.

If possible you should build your programs with maximum debug symbols generated and then strip them if you don't want or can't let your release versions to have them, but keep a copy of each released version with the debug symbols which you can couple with the core file if you need to debug a crash.

blocks|key|2557713|text|除了generating+a+stacktrace+in+a+SIGSEGV+handler和/或generating+a+core+dump之外，它也可能对find+where+an+uncaught+C%2B%2B+exception+is+thrown有用。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2557714|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/77005/how-to-generate-a-stacktrace-when-my-gcc-c-app-crashes|1|https://stackoverflow.com/questions/17965/generate-a-core-dump-in-linux|2|https://stackoverflow.com/questions/2443135/how-do-i-find-where-an-exception-was-thrown-in-c^0|V|7|2|18|0|1D|M|1|27|1A|2|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@$9|U|A|V|1|W]|$9|X|A|Y|1|Z]|$9|10|A|11|1|12]]|E|$]]|$1|F|3|-4|5|6|7|13|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]|N|$5|I|J|K|E|$L|O]]|P|$5|I|J|K|E|$L|Q]]]]

In addition to <a href="https://stackoverflow.com/questions/77005/how-to-generate-a-stacktrace-when-my-gcc-c-app-crashes">generating a stacktrace in a <code>SIGSEGV</code> handler</a> and/or <a href="https://stackoverflow.com/questions/17965/generate-a-core-dump-in-linux">generating a core dump</a>, it may also be useful to <a href="https://stackoverflow.com/questions/2443135/how-do-i-find-where-an-exception-was-thrown-in-c">find where an uncaught C++ exception is thrown</a>.

What is the best way to analyze crashes on Linux? 

We expect to build the software and deliver a release version to testers. The testers may not be able remember how to reproduce the crash or the crash may be totally intermittent. They also will not have a development environment on their machines. The software is written in C/C++ and compiled into native machine code for distribution.

Crash Analysis on Linux

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

分析Linux系统崩溃的最好方法是什么？我们希望构建该软件，并向测试人员提供一个发布版本。测试人员可能无法记住如何重现崩溃，或者崩溃可能完全是间歇性的。他们的机器上也不会有开发环境。该软件是用C/C++编写的，并编译成用于分发的本机代码。

问Linux系统的崩溃分析
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Linux系统的崩溃分析EN