[Bug demangler/97068] New: Can't demangle a certain symbl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97068 Bug ID: 97068 Summary: Can't demangle a certain symbl Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: demangler Assignee: unassigned at gcc dot gnu.org Reporter: cbiesinger at google dot com Target Milestone: --- (gdb) demangle _ZN4base8OptionalIN5blink10TestStructEEaSIRS2_EENSt4__Cr9enable_ifIXaantsr3std7is_sameINS6_9remove_cvINS6_16remove_referenceIT_E4typeEE4typeES3_EE5valuesr3std16is_constructibleIS2_SA_EE5valuesr3std13is_assignableIS5_SA_EE5valueoontL_ZNS6_17integral_constantIbLb0EE5valueEEntsr3std7is_sameINS6_5decayISA_E4typeES2_EE5valueERS3_E4typeEOSA_ Can't demangle "_ZN4base8OptionalIN5blink10TestStructEEaSIRS2_EENSt4__Cr9enable_ifIXaantsr3std7is_sameINS6_9remove_cvINS6_16remove_referenceIT_E4typeEE4typeES3_EE5valuesr3std16is_constructibleIS2_SA_EE5valuesr3std13is_assignableIS5_SA_EE5valueoontL_ZNS6_17integral_constantIbLb0EE5valueEEntsr3std7is_sameINS6_5decayISA_E4typeES2_EE5valueERS3_E4typeEOSA_" (gdb) However: llvm-cxxfilt-9 _ZN4base8OptionalIN5blink10TestStructEEaSIRS2_EENSt4__Cr9enable_ifIXaantsr3std7is_sameINS6_9remove_cvINS6_16remove_referenceIT_E4typeEE4typeES3_EE5valuesr3std16is_constructibleIS2_SA_EE5valuesr3std13is_assignableIS5_SA_EE5valueoontL_ZNS6_17integral_constantIbLb0EE5valueEEntsr3std7is_sameINS6_5decayISA_E4typeES2_EE5valueERS3_E4typeEOSA_ std::__Cr::enable_if<(((!(std::is_same::type>::type, base::Optional >::value)) && (std::is_constructible::value)) && (std::is_assignable::value)) && ((!(std::__Cr::integral_constant::value)) || (!(std::is_same::type, blink::TestStruct>::value))), base::Optional&>::type base::Optional::operator=(blink::TestStruct&)
[Bug demangler/70517] c++filt crashes when demangling a symbol
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70517 Christian Biesinger changed: What|Removed |Added CC||cbiesinger at google dot com --- Comment #5 from Christian Biesinger --- Using binutils from a month ago or so, this does not crash but also does not demangle...
[Bug demangler/81682] Timeout in demangler
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81682 Christian Biesinger changed: What|Removed |Added CC||cbiesinger at google dot com --- Comment #3 from Christian Biesinger --- In today's binutils, both those testcases run really quick in c++filt (cxxfilt).
[Bug demangler/85309] demangler failed with signal 11
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85309
Christian Biesinger changed:
What|Removed |Added
CC||cbiesinger at google dot com
--- Comment #1 from Christian Biesinger ---
This seems to not crash in GDB from today:
GNU gdb (GDB) 9.0.50.20191204-git
(gdb) set lang c++
(gdb) demangle
_ZSt7forwardIRZN3ftz6Engine20ClientNetworkHandler13ProcessEventsEvEUlRT_E_EOS3_RNSt16remove_referenceIS3_E4typeE
ftz::Engine::ClientNetworkHandler::ProcessEvents()::{lambda(auto:1&)#1}&
std::forward(std::remove_reference::type&)
quit)
[Bug demangler/88629] Regression lead to Heap-buffer-overflow problem in function d_expression_1 in cp-demangle.c, as demonstrated by c++filt
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88629 Christian Biesinger changed: What|Removed |Added CC||cbiesinger at google dot com --- Comment #6 from Christian Biesinger --- I can't reproduce this on any of the three testcases with today's binutils built with ASAN
[Bug demangler/89671] Demangling segfault
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89671 Christian Biesinger changed: What|Removed |Added CC||cbiesinger at google dot com --- Comment #2 from Christian Biesinger --- Hmm, this one crashes for me in c++filt 2.31.1 but not on today's trunk (though it doesn't demangle it into anything, either)
[Bug demangler/92453] write buffer overflow in cplus_demangle()
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92453 Christian Biesinger changed: What|Removed |Added CC||cbiesinger at google dot com --- Comment #2 from Christian Biesinger --- Could you send your patch to gcc-patches per https://gcc.gnu.org/contribute.html#patches ? Thanks!
[Bug demangler/84668] c++filt: out of memory allocating 18446744071696285694 bytes after a total of 135168 bytes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84668 Christian Biesinger changed: What|Removed |Added CC||cbiesinger at google dot com --- Comment #3 from Christian Biesinger --- Hmm this seems to be fixed on trunk for me, though still reproducible on 2.31.1
[Bug demangler/68159] Demangler crash (GDB PR 19190)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68159 Christian Biesinger changed: What|Removed |Added CC||cbiesinger at google dot com --- Comment #16 from Christian Biesinger --- Looks like the answer is yes, based on my testing.
[Bug demangler/68159] Demangler crash (GDB PR 19190)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68159 --- Comment #17 from Christian Biesinger --- Sorry, rather, none of these testcases seem to crash anymore but the one from comment 0 still does not demangle.
[Bug demangler/68700] demangler failed with signal 11
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68700 Christian Biesinger changed: What|Removed |Added CC||cbiesinger at google dot com --- Comment #3 from Christian Biesinger --- This does not seem to crash on binutils trunk, but it does not demangle either.
[Bug demangler/69094] erroneous demangling
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69094 Christian Biesinger changed: What|Removed |Added CC||cbiesinger at google dot com --- Comment #2 from Christian Biesinger --- Still happening.
[Bug demangler/82026] Undemanglable symbol
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82026 Christian Biesinger changed: What|Removed |Added CC||cbiesinger at google dot com --- Comment #2 from Christian Biesinger --- No longer crashes on binutils trunk, though it does crash 2.31.1. Trunk doesn't demangle it, though
[Bug demangler/87241] A hang problem for c++filt
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87241 Christian Biesinger changed: What|Removed |Added CC||cbiesinger at google dot com --- Comment #5 from Christian Biesinger --- This seems to be fixed on binutils trunk (in that it doesn't allocate lots of memory and just returns early), but not in 2.31.1
[Bug demangler/83495] Segmentation Fault - 63915465
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83495 Christian Biesinger changed: What|Removed |Added CC||cbiesinger at google dot com --- Comment #6 from Christian Biesinger --- The attachment contains a testcase: _ZZmmFoREES_ Current c++filt does not crash for me on that, but I don't know if it requires a specific setup or this is fixed.
[Bug debug/91888] New: GCC will write absolute paths into DW_AT_GNU_dwo_name even with -fdebug-prefix-map
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91888 Bug ID: 91888 Summary: GCC will write absolute paths into DW_AT_GNU_dwo_name even with -fdebug-prefix-map Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: debug Assignee: unassigned at gcc dot gnu.org Reporter: cbiesinger at google dot com Target Milestone: --- Created attachment 46939 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46939&action=edit testcase script $ readelf --debug-dump /tmp/outputs/foo [...] <20> DW_AT_GNU_dwo_name: (indirect string, offset: 0x0): /tmp/outputs/foo.dwo <24> DW_AT_comp_dir: . That's despite compiling with -fdebug-prefix-map=/tmp=. See the attached script that creates and compiles a simple c file. (this is with gcc from git trunk, revision e8f8842d90abe5eafa8c32f08fbc3a747a45747c from sep 24)
[Bug debug/91888] GCC will write absolute paths into DW_AT_GNU_dwo_name even with -fdebug-prefix-map
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91888 --- Comment #1 from Christian Biesinger --- (sorry, copied the wrong revision. it's actually ed342df533bf18eee2d5f84f1251a13f43d78505 from sep 21)
