调试dmesg日志

Question

我注意到我的日志里有下面的内容。我只是不知道如何解决或找出造成这些问题的原因，以及它们是否是严重的。

[582046.956291] Core dump to |/usr/libexec/abrt-hook-ccpp 7 0 18482 0 0 1379281138 e pipe failed
[582346.769892] Core dump to |/usr/libexec/abrt-hook-ccpp 7 0 21093 0 0 1379281439 e pipe failed
[582646.586134] Core dump to |/usr/libexec/abrt-hook-ccpp 7 0 23723 0 0 1379281739 e pipe failed
[582946.390029] Core dump to |/usr/libexec/abrt-hook-ccpp 7 0 26342 0 0 1379282039 e pipe failed
[583246.202851] Core dump to |/usr/libexec/abrt-hook-ccpp 7 0 29010 0 0 1379282340 e pipe failed
[583546.018408] Core dump to |/usr/libexec/abrt-hook-ccpp 7 0 31620 0 0 1379282640 e pipe failed
[583845.836688] Core dump to |/usr/libexec/abrt-hook-ccpp 7 0 1837 0 0 1379282940 e pipe failed
[584145.645968] Core dump to |/usr/libexec/abrt-hook-ccpp 7 0 4416 0 0 1379283241 e pipe failed
[584445.455705] Core dump to |/usr/libexec/abrt-hook-ccpp 7 0 7001 0 0 1379283541 e pipe failed
[584745.266532] Core dump to |/usr/libexec/abrt-hook-ccpp 7 0 9600 0 0 1379283841 e pipe failed
[585045.074399] Core dump to |/usr/libexec/abrt-hook-ccpp 7 0 12209 0 0 1379284141 e pipe failed
[585344.885464] Core dump to |/usr/libexec/abrt-hook-ccpp 7 0 14790 0 0 1379284442 e pipe failed
[585644.743818] Core dump to |/usr/libexec/abrt-hook-ccpp 7 0 17605 0 0 1379284742 e pipe failed
[585944.511572] Core dump to |/usr/libexec/abrt-hook-ccpp 7 0 20183 0 0 1379285042 e pipe failed
[586244.315990] Core dump to |/usr/libexec/abrt-hook-ccpp 7 0 22781 0 0 1379285343 e pipe failed
[586544.123020] Core dump to |/usr/libexec/abrt-hook-ccpp 7 0 25385 0 0 1379285643 e pipe failed
[586843.932084] Core dump to |/usr/libexec/abrt-hook-ccpp 7 0 27984 0 0 1379285943 e pipe failed
[587143.742379] Core dump to |/usr/libexec/abrt-hook-ccpp 7 0 30608 0 0 1379286244 e pipe failed
[587443.559349] Core dump to |/usr/libexec/abrt-hook-ccpp 7 0 799 0 0 1379286544 e pipe failed
[587743.373027] Core dump to |/usr/libexec/abrt-hook-ccpp 7 0 3420 0 0 1379286844 e pipe failed
[588043.175248] Core dump to |/usr/libexec/abrt-hook-ccpp 7 0 6031 0 0 1379287145 e pipe failed
[588342.986730] Core dump to |/usr/libexec/abrt-hook-ccpp 7 0 8665 0 0 1379287445 e pipe failed
[588642.795951] Core dump to |/usr/libexec/abrt-hook-ccpp 7 0 11279 0 0 1379287745 e pipe failed
[588942.608088] Core dump to |/usr/libexec/abrt-hook-ccpp 7 0 13915 0 0 1379288045 e pipe failed
[589242.420741] Core dump to |/usr/libexec/abrt-hook-ccpp 7 0 16728 0 0 1379288346 e pipe failed
[589542.235065] Core dump to |/usr/libexec/abrt-hook-ccpp 7 0 19355 0 0 1379288646 e pipe failed
[589842.061502] Core dump to |/usr/libexec/abrt-hook-ccpp 7 0 21998 0 0 1379288946 e pipe failed
[590141.856687] Core dump to |/usr/libexec/abrt-hook-ccpp 7 0 24657 0 0 1379289247 e pipe failed
[590441.700335] Core dump to |/usr/libexec/abrt-hook-ccpp 7 0 27307 0 0 1379289547 e pipe failed
[590741.483298] Core dump to |/usr/libexec/abrt-hook-ccpp 7 0 29944 0 0 1379289847 e pipe failed
[591041.286647] Core dump to |/usr/libexec/abrt-hook-ccpp 7 0 32554 0 0 1379290148 e pipe failed

Answer 1

当程序出现意外结果时，会生成一个核心转储。上面告诉您一个命令失败了，内存中的程序副本已经由abrt守护进程(命令/usr/libexec/abrt-hook-ccpp)处理。然后，可以使用诸如gdb之类的工具来调试故障。注: gdb不是为胆小的人！

这些通常是由于编写得不好的代码(它需要更好地处理异常)、内存不足问题，或者诸如命令与某个动态加载库相链接的潜在问题，而这个动态加载库现在已经被更改，崩溃的程序不能再以它期望的方式使用它。

在此页中，详细介绍了什么是Abrt过程，以及它如何处理核心。

当运行“abrtd”时，sysctl变量“kernel.core_pattern”的值与上面所示的值不同，如下所示：$sysctl -a|grep core_pattern kernel.core_pattern=/usr/libexec/abrt-钩子-ccpp /var/cache/abrt %p %s %u %c“abrtd”在目录“/var/cache/abrt”中创建一个子目录(名为“ccpp-1279914365-14618”)，如变量的值所示。这也意味着核心文件也将存储在“/var/cache/abrt”目录下的子目录中(除了运行应用程序的当前目录之外)。ABRT守护进程除了子目录中的核心转储文件之外，还创建其他文件，以进一步帮助用户调试崩溃问题。