[Bug c++/70481] [Regression] Libiberty Demangler segfaults

2016-05-19 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70481 --- Comment #6 from Jakub Jelinek --- Author: jakub Date: Thu May 19 12:05:41 2016 New Revision: 236456 URL: https://gcc.gnu.org/viewcvs?rev=236456=gcc=rev Log: Backported from mainline 2016-05-19 Jakub Jelinek

[Bug c++/70481] [Regression] Libiberty Demangler segfaults

2016-05-19 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70481 --- Comment #5 from Jakub Jelinek --- Author: jakub Date: Thu May 19 10:44:31 2016 New Revision: 236452 URL: https://gcc.gnu.org/viewcvs?rev=236452=gcc=rev Log: Backported from mainline 2016-05-19 Jakub Jelinek

[Bug c++/70481] [Regression] Libiberty Demangler segfaults

2016-03-31 Thread law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70481 Jeffrey A. Law changed: What|Removed |Added CC||brian.carpenter at gmail dot com ---

[Bug c++/70481] [Regression] Libiberty Demangler segfaults

2016-03-31 Thread law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70481 Jeffrey A. Law changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|

[Bug c++/70481] [Regression] Libiberty Demangler segfaults

2016-03-31 Thread boehme.marcel at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70481 --- Comment #2 from Marcel Böhme --- These are two distinct bugs. During fuzzing the btypevec bug appears more often. But it seemed less critical since only NULL is written to the freed memory: work -> btypevec[ret] = NULL; On the other hand,

[Bug c++/70481] [Regression] Libiberty Demangler segfaults

2016-03-31 Thread miyuki at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70481 Mikhail Maltsev changed: What|Removed |Added CC||miyuki at gcc dot gnu.org --- Comment