I received the following error when starting cuda-gdb against our test suite:
NVIDIA (R) CUDA Debugger
10.2 release
Portions Copyright (C) 2007-2019 NVIDIA Corporation
GNU gdb (GDB) 7.12
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./build/tests/run...cuda-gdb/7.12/gdb/cp-support.c:1600: demangler-warning: unable to demangle '_ZSt7forwardIRZN2xt17xfunction_stepperINS0_6detail7iscloseEJRKNS0_14xarray_adaptorIRSt6vectorIdSaIdEELNS0_11layout_typeE1ES5_ImSaImEENS0_22xtensor_expression_tagEEESF_EE4stepEmEUlRT_E_EOSH_RNSt16remove_referenceISH_E4typeE' (demangler failed with signal 11)
Unable to dump core, use `ulimit -c unlimited' before executing GDB next time.
cuda-gdb/7.12/gdb/cp-support.c:1615: demangler-warning: unable to demangle '_ZSt7forwardIRZN2xt17xfunction_stepperINS0_6detail7iscloseEJRKNS0_14xarray_adaptorIRSt6vectorIdSaIdEELNS0_11layout_typeE1ES5_ImSaImEENS0_22xtensor_expression_tagEEESF_EE4stepEmEUlRT_E_EOSH_RNSt16remove_referenceISH_E4typeE' (demangler failed with signal 11)
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y
This is a bug, please report it. For instructions, see:
<http://www.gnu.org/software/gdb/bugs/>.
You may reproduce the error by writing a small program using xtensor’s xt::allclose
function.
The cause is probably 68159 – Demangler crash (GDB PR 19190) which was fixed 3 years ago in gdb>=8 gcc.gnu.org Git - gcc.git/commit
Just here to say that I’m getting the same issue after I did an update to my system. My issue is also with xtensor. Here’s my output. Were you able to work around this?
NVIDIA (R) CUDA Debugger
10.2 release
Portions Copyright (C) 2007-2019 NVIDIA Corporation
GNU gdb (GDB) 7.12
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ../openmc-plusultra...done.
(cuda-gdb) r
Starting program: /home/gavin/Code/openmc-plusultra/openmc-plusultra
cuda-gdb/7.12/gdb/cp-support.c:1600: demangler-warning: unable to demangle '_ZSt7forwardIRZNK2xt9xfunctionINS0_6detail10multipliesEJNS0_7xscalarIRKdEERKNS0_17xtensor_containerINS0_7uvectorIdSaIdEEELm4ELNS0_11layout_typeE1ENS0_22xtensor_expression_tagEEEEE17has_linear_assignISt5arrayIlLm4EEEEbRKT_EUlbOSL_E_ESO_RNSt16remove_referenceISL_E4typeE' (demangler failed with signal 11)
Attempting to dump core.
cuda-gdb/7.12/gdb/cp-support.c:1615: demangler-warning: unable to demangle '_ZSt7forwardIRZNK2xt9xfunctionINS0_6detail10multipliesEJNS0_7xscalarIRKdEERKNS0_17xtensor_containerINS0_7uvectorIdSaIdEEELm4ELNS0_11layout_typeE1ENS0_22xtensor_expression_tagEEEEE17has_linear_assignISt5arrayIlLm4EEEEbRKT_EUlbOSL_E_ESO_RNSt16remove_referenceISL_E4typeE' (demangler failed with signal 11)
A problem internal to GDB has been detected,
This was a problem with cuda-gdb based on GDB 7.12 found in CUDA Toolkit 10.2 and earlier.
This and the underlying bug was fixed in GDB/8.x. Please retry with the cuda-gdb based on GDB 8.2 found in CUDA Toolkit 11.0 and later.
1 Like