Bug 1367131

Summary: Unable to demangle function when debugging OpenCL code
Product: [Fedora] Fedora Reporter: James Paul Turner <jamesturner246>
Component: gdbAssignee: Jan Kratochvil <jan.kratochvil>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: bugzilla, gbenson, jan.kratochvil, mcatanzaro+wrong-account-do-not-cc, nmiell, orion, palves, pmuldoon, sergiodj, tom
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 16:33:20 UTC Type: Bug
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

Description James Paul Turner 2016-08-15 16:02:40 UTC
Description of problem:
When debugging an OpenCL program (CUDA platform), a call to clGetPlatformIDs() triggers the following error:

../../gdb/cp-support.c:1595: demangler-warning: unable to demangle '_ZNK6clover6detail11basic_rangeINS_13adaptor_rangeIZNS_6kernel6
launchERNS_13command_queueERKSt6vectorImSaImEESA_SA_EUlmE_JRS8_EEENS0_16iterator_adaptorISB_JN9__gnu_cxx17__normal_iteratorIPmS8_EE
EEESJ_EcvT_IS6_IPjSaISN_EEvEEv' (demangler failed with signal 11)
Unable to dump core, use `ulimit -c unlimited' before executing GDB next time.
Missing separate debuginfos, use: dnf debuginfo-install mesa-libOpenCL-12.0.1-1.fc24.x86_64
../../gdb/cp-support.c:1608: demangler-warning: unable to demangle '_ZNK6clover6detail11basic_rangeINS_13adaptor_rangeIZNS_6kernel6
launchERNS_13command_queueERKSt6vectorImSaImEESA_SA_EUlmE_JRS8_EEENS0_16iterator_adaptorISB_JN9__gnu_cxx17__normal_iteratorIPmS8_EE
EEESJ_EcvT_IS6_IPjSaISN_EEvEEv' (demangler failed with signal 11)
A problem internal to GDB has been detected,
further debugging may prove unreliable.


Version-Release number of selected component (if applicable):
GNU gdb (GDB) Fedora 7.11.1-75.fc24

How reproducible:
Every time.

Steps to Reproduce:
1. Call clGetPlatformIDs from an OpenCL C++ program


Additional info:
The computer has both NVIDIA CUDA and Clover (Mesa) OpenCL platforms.

Comment 1 Jan Kratochvil 2016-08-15 16:13:12 UTC
*** Bug 1364588 has been marked as a duplicate of this bug. ***

Comment 2 Jan Kratochvil 2016-09-18 22:26:12 UTC
*** Bug 1377020 has been marked as a duplicate of this bug. ***

Comment 3 Jan Kratochvil 2017-01-22 12:05:53 UTC
*** Bug 1415475 has been marked as a duplicate of this bug. ***

Comment 4 Michael Catanzaro 2017-02-11 18:15:56 UTC
Similar problem has been detected:

It crashes 100% of the time whenever opening a coredump of any program that links to WebKitGTK+.

reporter:       libreport-2.8.0
backtrace_rating: 4
cmdline:        gdb /home/mcatanzaro/Projects/GNOME/install/libexec/webkit2gtk-4.0/WebKitWebProcess /var/tmp/coredump-SEBGX0
crash_function: dump_core
executable:     /usr/libexec/gdb
journald_cursor: s=45244fb925ea45daab479b341ea11219;i=1272f4;b=173c429961314f21a8dfd9081929dd9c;m=39296cacb;t=5484524707b71;x=e8e147b16f029ab8
kernel:         4.9.8-201.fc25.x86_64
package:        gdb-headless-7.12.1-41.fc25
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
reason:         gdb killed by signal 6
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 5 Michael Catanzaro 2017-02-11 18:16:03 UTC
Created attachment 1249387 [details]
File: backtrace

Comment 6 Jan Kratochvil 2017-03-15 20:58:33 UTC
FYI there is now an upstream fix of the crash:
  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72822#c6
I have not backported it yet as I would like to verify first it provides valid output.  I still find better to crash than to provide invalid output, that is more difficult to debug.

Comment 7 M. Edward (Ed) Borasky 2017-04-26 06:54:27 UTC
I've got this on Fedora 26 alpha - trying to debug a clpeak issue bug 1433632.

Comment 8 Michael Catanzaro 2017-06-05 16:20:22 UTC
(In reply to Jan Kratochvil from comment #6)
> FYI there is now an upstream fix of the crash:
>   https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72822#c6
> I have not backported it yet as I would like to verify first it provides
> valid output.  I still find better to crash than to provide invalid output,
> that is more difficult to debug.

Bug #1377020, marked a duplicate of this, is tracked upstream as #68159, which is still open. I don't know whether they are duplicates or separate issues.

Comment 9 Fedora End Of Life 2017-07-25 22:26:24 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 Fedora  'version'
of '24'.

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

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 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, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 10 Fedora End Of Life 2017-08-08 16:33:20 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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. If you experience problems, please add a comment to this
bug.

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