Bug 1476741

Summary: [abrt] clinfo: operator delete(): clinfo killed by signal 6
Product: [Fedora] Fedora Reporter: Paul DeStefano <prd-fedora>
Component: llvmAssignee: Tom Stellard <tstellar>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: ajax, besser82, bos, davejohansen, dmalcolm, fabian.deutsch, ignatenko, jistone, petersen, scottt.tw, siddharth.kde, tschelle, tstellar
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/37ed97643fde035b496842b72a1071b4a9e848bf
Whiteboard: abrt_hash:9d847743897e1c6f0180462b96b6f5576ef286e7;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-05 14:38:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Paul DeStefano 2017-07-31 10:21:35 UTC 
Description of problem:
Just ran clinfo.  

Version-Release number of selected component:
clinfo-2.2.17.06.14-1.fc26

Additional info:
reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        clinfo
crash_function: operator delete
executable:     /usr/bin/clinfo
journald_cursor: s=61b870d8c6864ac1a90e6a00b3904e1a;i=ef696;b=1f8cff23d9d3481dab03a4ff8b2feee3;m=691bbf8b71;t=55599fd7d7d1e;x=d9cb6d4709e1b4ff
kernel:         4.11.11-300.fc26.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            13013
Comment 1 Paul DeStefano 2017-07-31 10:21:41 UTC 
Created attachment 1306988 [details]
File: backtrace
Comment 2 Paul DeStefano 2017-07-31 10:21:42 UTC 
Created attachment 1306989 [details]
File: cgroup
Comment 3 Paul DeStefano 2017-07-31 10:21:43 UTC 
Created attachment 1306990 [details]
File: core_backtrace
Comment 4 Paul DeStefano 2017-07-31 10:21:44 UTC 
Created attachment 1306991 [details]
File: cpuinfo
Comment 5 Paul DeStefano 2017-07-31 10:21:46 UTC 
Created attachment 1306992 [details]
File: dso_list
Comment 6 Paul DeStefano 2017-07-31 10:21:47 UTC 
Created attachment 1306993 [details]
File: environ
Comment 7 Paul DeStefano 2017-07-31 10:21:48 UTC 
Created attachment 1306994 [details]
File: limits
Comment 8 Paul DeStefano 2017-07-31 10:21:49 UTC 
Created attachment 1306995 [details]
File: maps
Comment 9 Paul DeStefano 2017-07-31 10:21:50 UTC 
Created attachment 1306996 [details]
File: open_fds
Comment 10 Paul DeStefano 2017-07-31 10:21:51 UTC 
Created attachment 1306997 [details]
File: proc_pid_status
Comment 11 Paul DeStefano 2017-07-31 10:21:52 UTC 
Created attachment 1306999 [details]
File: var_log_messages
Comment 12 Igor Gnatenko 2017-07-31 10:55:27 UTC 
seems like bug in LLVM
Comment 13 Paul DeStefano 2017-07-31 18:19:28 UTC 
Yes!  Oh, please please help fix this.  BOINC has been broken for over a year, now, and, even after kernel, mesa, and LLVM, and hardware upgrades, I still get LLVM errors.
Comment 14 Tom Stellard 2017-08-25 21:50:52 UTC 
I've found that uninstalling beignet fixed the crash for me.  But also when I re-installed beignet, the crash did not happen either.
Comment 15 Paul DeStefano 2017-08-25 22:23:12 UTC 
Hmm, that's very interesting.  I removed beinget and clinfo doesn't crash for me either, now.

But, how did this help clinfo?

I hope we can still leave this open for LLVM, though, since I have other LLVM problems.  I would double check BOINC soon.
Comment 16 Tom Stellard 2017-08-25 22:30:17 UTC 
(In reply to Paul DeStefano from comment #15)
> Hmm, that's very interesting.  I removed beinget and clinfo doesn't crash
> for me either, now.
> 
> But, how did this help clinfo?
> 

My guess is that since beignet statically links llvm/clang and was exporting some clang/llvm symbols that pocl ended up using.  This would be another problem that symbol versioning for LLVM might fix.

> I hope we can still leave this open for LLVM, though, since I have other
> LLVM problems.  I would double check BOINC soon.

If you have other LLVM problems, you should file new bugs for them.
Comment 17 Tom Stellard 2018-03-23 13:39:06 UTC 
This is fixed on rawhide by pocl-1.1-1.fc29.x86_64.rpm.
Comment 18 Tom Stellard 2018-03-23 13:43:28 UTC 
I think this was fixed by enabling symbol versioning on libLLVM.so.  This is too big of a change to backport to f26,f27, so this fix will first appear in f28.
Comment 19 Fedora Update System 2018-04-02 14:21:49 UTC 
pocl-1.1-2.fc28 lldb-6.0.0-3.fc28 clang-6.0.0-5.fc28 llvm-6.0.0-11.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-02c4091319
Comment 20 Fedora Update System 2018-04-03 15:57:24 UTC 
clang-6.0.0-5.fc28, lldb-6.0.0-3.fc28, llvm-6.0.0-11.fc28, mesa-18.0.0-2.fc28.1, pocl-1.1-2.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-02c4091319
Comment 21 Fedora Update System 2018-04-03 23:25:39 UTC 
clang-6.0.0-5.fc28 lldb-6.0.0-3.fc28 llvm-6.0.0-11.fc28 mesa-18.0.0-3.fc28 pocl-1.1-2.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-02c4091319
Comment 22 Fedora Update System 2018-04-04 18:35:19 UTC 
clang-6.0.0-5.fc28, lldb-6.0.0-3.fc28, llvm-6.0.0-11.fc28, mesa-18.0.0-3.fc28, pocl-1.1-2.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-02c4091319
Comment 23 Fedora Update System 2018-04-05 11:48:00 UTC 
clang-6.0.0-5.fc28, lldb-6.0.0-3.fc28, llvm-6.0.0-11.fc28, mesa-18.0.0-3.fc28, pocl-1.1-2.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.