Support #19287
un-demangleable symbol
100%
Description
Debugging with gdb I got this:
/home/greenc/work/cet-is/test-products/gdb/v7_12/src/gdb-7.12/gdb/cp-support.c:1615: demangler-warning: unable to demangle '_ZSt7forwardIRZN3art19TriggerNamesServiceC4ERKN5fhicl12ParameterSetERKSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaISC_EEEUlRT_mRKT0_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) n
things seemed to work OK after I continued, but it's an inconvenience.
SL6's built in c++filt can't understand this symbol either, but it doesn't crash.
Related issues
History
#1 Updated by Kyle Knoepfel almost 3 years ago
- Tracker changed from Bug to Support
- Status changed from New to Feedback
gdb 7.12 is known to suffer from the inability to demangle symbols generated by more modern compilers. Please use gdb 8.0.1 instead and let us know if there is still an issue (http://scisoft.fnal.gov/scisoft/packages/gdb/v8_0_1/).
#2 Updated by Kyle Knoepfel almost 3 years ago
- Has duplicate Support #17751: a problem with debugging art v2_07-based executables with gdb added
#3 Updated by Kyle Knoepfel almost 3 years ago
- Has duplicate deleted (Support #17751: a problem with debugging art v2_07-based executables with gdb)
#4 Updated by Kyle Knoepfel almost 3 years ago
- Is duplicate of Support #17751: a problem with debugging art v2_07-based executables with gdb added
#5 Updated by Christopher Backhouse almost 3 years ago
Seems like this is just an oversight on our side. We explicitly specify gdb v7_12.
Is there some source for a newer c++filt we could use, or a replacement command?
#6 Updated by Kyle Knoepfel almost 3 years ago
Chris Green has provided an SLF6 version for DUNE. I've copied it here:
novagpvm01.fnal.gov:~knoepfel/c++filt
We have not yet found a way to generally package it, though.
#7 Updated by Christopher Backhouse almost 3 years ago
Works, though I'm not sure it's a big improvement :)
Thanks!
$ ~knoepfel/c++filt _ZSt7forwardIRZN3art19TriggerNamesServiceC4ERKN5fhicl12ParameterSetERKSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaISC_EEEUlRT_mRKT0_E_EOSH_RNSt16remove_referenceISH_E4typeE
art::TriggerNamesService::TriggerNamesService(fhicl::ParameterSet const&, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&)::{lambda(auto:1&, unsigned long, auto:2 const&)#1}& std::forward<art::TriggerNamesService::TriggerNamesService(fhicl::ParameterSet const&, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&)::{lambda(auto:1&, unsigned long, auto:2 const&)#1}&>(std::remove_reference<art::TriggerNamesService::TriggerNamesService(fhicl::ParameterSet const&, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&)::{lambda(auto:1&, unsigned long, auto:2 const&)#1}&>::type&)
#8 Updated by Kyle Knoepfel almost 3 years ago
- Status changed from Feedback to Closed
Agreed. :)
If you think it's worth having a packaged c++filt, then please go ahead and fill out a feature request.
#9 Updated by Kyle Knoepfel almost 3 years ago
- Assignee set to Kyle Knoepfel
- % Done changed from 0 to 100