Check for null result from gdb_demangle
authorAli Tamur via gdb-patches <gdb-patches@sourceware.org>
Fri, 21 Feb 2020 15:19:21 +0000 (08:19 -0700)
committerTom Tromey <tromey@adacore.com>
Fri, 21 Feb 2020 15:19:21 +0000 (08:19 -0700)
commit4f180d5396741eb65badba70cf5077b7d48f8641
tree5a3f0c334bda24bf85212f15e86a6b5799b6cb03
parenta4425a57c7ad127b30cdfe271c870d5c8ebcfad7
Check for null result from gdb_demangle

I am sending this patch on behalf of kmoy@google.com, who discovered the bug
and wrote the fix.

gdb_demangle can return null for strings that don't properly demangle. The null
check was mistakenly removed in commit 43816ebc335. Without this check, GDB
aborts when loading symbols from some binaries.

gdb/ChangeLog
2020-02-21  Ali Tamur  <tamur@google.com>

* dwarf2/read.c (dwarf2_name): Add null check.
gdb/ChangeLog
gdb/dwarf2/read.c