aboutsummaryrefslogtreecommitdiff
path: root/config/progtest.m4
diff options
context:
space:
mode:
authorAndrew Burgess <aburgess@broadcom.com>2014-05-27 11:57:33 +0100
committerPedro Alves <palves@redhat.com>2014-06-11 11:41:51 +0100
commit173373c6f6388171d1d62a217fae90a052395be2 (patch)
tree5af385b647b127628d2fbd0f4e8426bb82fe79fd /config/progtest.m4
parent364fe1f72265eb54bce08511233d06ed48e9c41a (diff)
downloadgdb-173373c6f6388171d1d62a217fae90a052395be2.zip
gdb-173373c6f6388171d1d62a217fae90a052395be2.tar.gz
gdb-173373c6f6388171d1d62a217fae90a052395be2.tar.bz2
Delete temporary string within demangler even in failure cases.gdb-7.8-branchpoint
A call to demangle_template might allocate storage within a temporary string even if the call to demangle_template eventually returns failure. This will never cause the demangler to crash, but does leak memory, as a result I've not added any tests for this. Calling string_delete is safe, even if nothing is allocated into the string, the string is initialised with string_init, so we know the internal pointers are NULL. libiberty/ChangeLog * cplus-dem.c (do_type): Call string_delete even if the call to demangle_template fails.
Diffstat (limited to 'config/progtest.m4')
0 files changed, 0 insertions, 0 deletions