aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.dwarf2/cpp-linkage-name.c
diff options
context:
space:
mode:
authorAli Tamur via gdb-patches <gdb-patches@sourceware.org>2020-02-21 08:19:21 -0700
committerTom Tromey <tromey@adacore.com>2020-02-21 08:19:21 -0700
commit4f180d5396741eb65badba70cf5077b7d48f8641 (patch)
tree5a3f0c334bda24bf85212f15e86a6b5799b6cb03 /gdb/testsuite/gdb.dwarf2/cpp-linkage-name.c
parenta4425a57c7ad127b30cdfe271c870d5c8ebcfad7 (diff)
downloadbinutils-4f180d5396741eb65badba70cf5077b7d48f8641.zip
binutils-4f180d5396741eb65badba70cf5077b7d48f8641.tar.gz
binutils-4f180d5396741eb65badba70cf5077b7d48f8641.tar.bz2
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.
Diffstat (limited to 'gdb/testsuite/gdb.dwarf2/cpp-linkage-name.c')
0 files changed, 0 insertions, 0 deletions