public inbox for src-cvs@sourceware.org help / color / mirror / Atom feed
From: palves@sourceware.org To: src-cvs@sourceware.org Subject: gdb and binutils branch master updated. 173373c6f6388171d1d62a217fae90a052395be2 Date: Wed, 11 Jun 2014 11:00:00 -0000 [thread overview] Message-ID: <20140611110051.14706.qmail@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gdb and binutils". The branch, master has been updated via 173373c6f6388171d1d62a217fae90a052395be2 (commit) from 364fe1f72265eb54bce08511233d06ed48e9c41a (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=173373c6f6388171d1d62a217fae90a052395be2 commit 173373c6f6388171d1d62a217fae90a052395be2 Author: Andrew Burgess <aburgess@broadcom.com> Date: Tue May 27 11:57:33 2014 +0100 Delete temporary string within demangler even in failure cases. 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. ----------------------------------------------------------------------- Summary of changes: libiberty/ChangeLog | 5 +++++ libiberty/cplus-dem.c | 5 ++++- 2 files changed, 9 insertions(+), 1 deletions(-) hooks/post-receive -- gdb and binutils
reply other threads:[~2014-06-11 11:00 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20140611110051.14706.qmail@sourceware.org \ --to=palves@sourceware.org \ --cc=src-cvs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).