[Bug demangler/97068] New: Can't demangle a certain symbl

ngler Assignee: unassigned at gcc dot gnu.org Reporter: cbiesinger at google dot com Target Milestone: --- (gdb) dem

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[Bug debug/91888] New: GCC will write absolute paths into DW_AT_GNU_dwo_name even with -fdebug-prefix-map

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

[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)