Disclaimer: In Linux by default this feature is turned off. Some time ago I've needed to turn it on. And it stayed so.
I've configure writing cores in right way: /etc/sysctl.conf : kernel.core_pattern = /tmp/cores/core_%e-%s.%p
I.e. core files are written in specially created subdirectory in /tmp. Filename provides name of crashed binary, signal it was killed and numeric pid of crashed process.
While debugging git build, I've find, that some process crashes. See bug #38 for details. This crash looks to be not critical. And isn't uniq, I've find similiar crashes on install some other packages.
Further check showed, that similiar crash appears on building CDE-2.2.2.
I can't guess which utility provides this crash, so I can't get gdb backtrace.
The only thing I find is that current directory (where is written core file in default) is:
cde-2.2.2/programs/dtksh/ksh93/src/lib/libast/core_30503.exe-6.31297
Process' name is '30503.exe' (numeric value should differ on another check).
Signal killed — 6 (SIGABRT).
My system uses:
sys-libs/glibc-2.19-r1
sys-devel/gcc-4.7.3-r1
Probably important dependency:
app-shells/ksh-93.20120229
My first question: does this issue reproduces in *BSD systems (using gcc and clang)?
The second is about level of this core: is it non-critical, or just looks so?
And the third question is about how to find the crashing binary to get dgb backtrace of core?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Disclaimer: In Linux by default this feature is turned off. Some time ago I've needed to turn it on. And it stayed so.
I've configure writing cores in right way:
/etc/sysctl.conf :
kernel.core_pattern = /tmp/cores/core_%e-%s.%p
I.e. core files are written in specially created subdirectory in /tmp. Filename provides name of crashed binary, signal it was killed and numeric pid of crashed process.
While debugging git build, I've find, that some process crashes. See bug #38 for details. This crash looks to be not critical. And isn't uniq, I've find similiar crashes on install some other packages.
Further check showed, that similiar crash appears on building CDE-2.2.2.
I can't guess which utility provides this crash, so I can't get gdb backtrace.
The only thing I find is that current directory (where is written core file in default) is:
cde-2.2.2/programs/dtksh/ksh93/src/lib/libast/core_30503.exe-6.31297
Process' name is '30503.exe' (numeric value should differ on another check).
Signal killed — 6 (SIGABRT).
My system uses:
sys-libs/glibc-2.19-r1
sys-devel/gcc-4.7.3-r1
Probably important dependency:
app-shells/ksh-93.20120229
My first question: does this issue reproduces in *BSD systems (using gcc and clang)?
The second is about level of this core: is it non-critical, or just looks so?
And the third question is about how to find the crashing binary to get dgb backtrace of core?
gcc-4.8.5, glibc-2.20, recent git build.
This issue looks to be fixed.