Bug 2005044 - [abrt] ccache: handle_failed_assertion(): ccache killed by SIGABRT
Summary: [abrt] ccache: handle_failed_assertion(): ccache killed by SIGABRT
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: ccache
Version: 34
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michael Cullen
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:b6feaa114e59750b33b68c91028...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-16 15:33 UTC by Jim Cromie
Modified: 2022-06-07 23:57 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-06-07 23:57:10 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (31.00 KB, text/plain)
2021-09-16 15:33 UTC, Jim Cromie
no flags Details
File: core_backtrace (3.27 KB, text/plain)
2021-09-16 15:33 UTC, Jim Cromie
no flags Details
File: cpuinfo (2.50 KB, text/plain)
2021-09-16 15:33 UTC, Jim Cromie
no flags Details
File: dso_list (816 bytes, text/plain)
2021-09-16 15:33 UTC, Jim Cromie
no flags Details
File: environ (9.34 KB, text/plain)
2021-09-16 15:33 UTC, Jim Cromie
no flags Details
File: limits (1.29 KB, text/plain)
2021-09-16 15:33 UTC, Jim Cromie
no flags Details
File: maps (3.99 KB, text/plain)
2021-09-16 15:33 UTC, Jim Cromie
no flags Details
File: mountinfo (2.42 KB, text/plain)
2021-09-16 15:33 UTC, Jim Cromie
no flags Details
File: open_fds (221 bytes, text/plain)
2021-09-16 15:33 UTC, Jim Cromie
no flags Details
File: proc_pid_status (1.39 KB, text/plain)
2021-09-16 15:33 UTC, Jim Cromie
no flags Details

Description Jim Cromie 2021-09-16 15:33:13 UTC
Description of problem:
dunno. wa

Version-Release number of selected component:
ccache-4.2-1.fc34

Additional info:
reporter:       libreport-2.15.2
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-org.gnome.Terminal.slice/vte-spawn-5db1bdc1-51a7-4858-a6bd-4bda160b1f0e.scope
cmdline:        gcc -Wp,-MMD,arch/x86/events/amd/.core.o.d -nostdinc -isystem /usr/lib/gcc/x86_64-redhat-linux/11/include -I/home/jimc/projects/lx/wk-next/arch/x86/include -I./arch/x86/include/generated -I/home/jimc/projects/lx/wk-next/include -I./include -I/home/jimc/projects/lx/wk-next/arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I/home/jimc/projects/lx/wk-next/include/uapi -I./include/generated/uapi -include /home/jimc/projects/lx/wk-next/include/linux/compiler-version.h -include /home/jimc/projects/lx/wk-next/include/linux/kconfig.h -include /home/jimc/projects/lx/wk-next/include/linux/compiler_types.h -D__KERNEL__ -fmacro-prefix-map=/home/jimc/projects/lx/wk-next/= -Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE -Werror=implicit-function-declaration -Werror=implicit-int -Werror=return-type -Wno-format-security -std=gnu89 -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -fcf-protection=none -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -fno-jump-tables -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -Wno-address-of-packed-member -O2 -fno-allow-store-data-races -fno-reorder-blocks -fno-ipa-cp-clone -fno-partial-inlining -Wframe-larger-than=2048 -fstack-protector-strong -Wimplicit-fallthrough=5 -Wno-unused-but-set-variable -Wno-unused-const-variable -fno-stack-clash-protection -g -gdwarf-4 -gz=zlib -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY -fno-inline-functions-called-once -Wdeclaration-after-statement -Wvla -Wno-pointer-sign -Wno-stringop-truncation -Wno-zero-length-bounds -Wno-array-bounds -Wno-stringop-overflow -Wno-restrict -Wno-maybe-uninitialized -fno-strict-overflow -fno-stack-check -fconserve-stack -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -Wno-packed-not-aligned -fsanitize=kernel-address -fasan-shadow-offset=0xdffffc0000000000 --param asan-globals=1 --param asan-instrumentation-with-call-threshold=0 --param asan-stack=1 --param asan-instrument-allocas=1 -I /home/jimc/projects/lx/wk-next/arch/x86/events/amd -I ./arch/x86/events/amd -DKBUILD_MODFILE="arch/x86/events/amd/core" -DKBUILD_BASENAME="core" -DKBUILD_MODNAME="core" -D__KBUILD_MODNAME=kmod_core -c -o arch/x86/events/amd/core.o /home/jimc/projects/lx/wk-next/arch/x86/events/amd/core.c
crash_function: handle_failed_assertion
executable:     /usr/bin/ccache
journald_cursor: s=8819bcd740424051846977471e8f5346;i=507832;b=ff53343b2df64ead99831f9c2503fc60;m=277a2cc0fc;t=5c95371453c06;x=aa06520d41b09f03
kernel:         5.14.0-rc4-lm1-00009-g6ffb90a167c2
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 handle_failed_assertion at /usr/src/debug/ccache-4.2-1.fc34.x86_64/src/assertions.cpp:38
 #3 SignalHandler::on_signal at /usr/src/debug/ccache-4.2-1.fc34.x86_64/src/SignalHandler.cpp:82
 #5 __pthread_sigmask at pthread_sigmask.c:44
 #6 __sigprocmask at ../sysdeps/unix/sysv/linux/sigprocmask.c:25
 #7 SignalHandler::unblock_signals at /usr/src/debug/ccache-4.2-1.fc34.x86_64/src/SignalHandler.cpp:134
 #8 SignalHandlerBlocker::~SignalHandlerBlocker at /usr/src/debug/ccache-4.2-1.fc34.x86_64/src/SignalHandler.cpp:143
 #9 Context::unlink_pending_tmp_files at /usr/src/debug/ccache-4.2-1.fc34.x86_64/src/Context.cpp:70
 #10 Context::~Context at /usr/src/debug/ccache-4.2-1.fc34.x86_64/src/Context.cpp:45
 #11 cache_compilation at /usr/src/debug/ccache-4.2-1.fc34.x86_64/src/ccache.cpp:2289
 #12 ccache_main at /usr/src/debug/ccache-4.2-1.fc34.x86_64/src/ccache.cpp:2823

Comment 1 Jim Cromie 2021-09-16 15:33:17 UTC
Created attachment 1823594 [details]
File: backtrace

Comment 2 Jim Cromie 2021-09-16 15:33:18 UTC
Created attachment 1823595 [details]
File: core_backtrace

Comment 3 Jim Cromie 2021-09-16 15:33:19 UTC
Created attachment 1823596 [details]
File: cpuinfo

Comment 4 Jim Cromie 2021-09-16 15:33:20 UTC
Created attachment 1823597 [details]
File: dso_list

Comment 5 Jim Cromie 2021-09-16 15:33:21 UTC
Created attachment 1823598 [details]
File: environ

Comment 6 Jim Cromie 2021-09-16 15:33:22 UTC
Created attachment 1823599 [details]
File: limits

Comment 7 Jim Cromie 2021-09-16 15:33:23 UTC
Created attachment 1823600 [details]
File: maps

Comment 8 Jim Cromie 2021-09-16 15:33:24 UTC
Created attachment 1823601 [details]
File: mountinfo

Comment 9 Jim Cromie 2021-09-16 15:33:25 UTC
Created attachment 1823602 [details]
File: open_fds

Comment 10 Jim Cromie 2021-09-16 15:33:26 UTC
Created attachment 1823603 [details]
File: proc_pid_status

Comment 11 Ben Cotton 2022-05-12 16:13:45 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 12 Ben Cotton 2022-06-07 23:57:10 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.