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.
*** Bug 1364588 has been marked as a duplicate of this bug. ***
*** Bug 1377020 has been marked as a duplicate of this bug. ***
*** Bug 1415475 has been marked as a duplicate of this bug. ***
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
Created attachment 1249387 [details] File: backtrace
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.
I've got this on Fedora 26 alpha - trying to debug a clpeak issue bug 1433632.
(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.
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.
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.