public inbox for
help / color / mirror / Atom feed
Subject: gdb and binutils branch master updated. 6143b8235e8d14685d8ab747cdd4f8faa94d1fe0
Date: Wed, 28 May 2014 22:08:00 -0000	[thread overview]
Message-ID: <> (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  6143b8235e8d14685d8ab747cdd4f8faa94d1fe0 (commit)
       via  6e933ccc75f683a19dda3c92c6d9a35f857b98b3 (commit)
       via  0aaa9a3aa1e68d309a4746633494b9a01a0575f5 (commit)
      from  7f3c034326ce5d487e897826a12c3a4b9d457b49 (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 -----------------------------------------------------------------;h=6143b8235e8d14685d8ab747cdd4f8faa94d1fe0

commit 6143b8235e8d14685d8ab747cdd4f8faa94d1fe0
Author: Pedro Alves <>
Date:   Wed May 28 23:06:44 2014 +0100

    Fix demangler testsuite crashes with CP_DEMANGLE_DEBUG defined
    Running the demangler's testsuite with CP_DEMANGLE_DEBUG defined
    crashes, with:
     Program received signal SIGSEGV, Segmentation fault.
     0x000000000040a8c3 in d_dump (dc=0x1, indent=12) at ../../src/libiberty/cp-demangle.c:567
     567       switch (dc->type)
     (gdb) bt 3
     #0  0x000000000040a8c3 in d_dump (dc=0x1, indent=12) at ../../src/libiberty/cp-demangle.c:567
     #1  0x000000000040ae47 in d_dump (dc=0x7fffffffd098, indent=10) at ../../src/libiberty/cp-demangle.c:787
     #2  0x000000000040ae47 in d_dump (dc=0x7fffffffd0c8, indent=8) at ../../src/libiberty/cp-demangle.c:787
    Note dc=0x1, which is obviously a bogus pointer.  This is the end of
    d_dump recursing for a component type that that doesn't actually have
     787       d_dump (d_left (dc), indent + 2);
     788       d_dump (d_right (dc), indent + 2);
    This fixes the two cases the testsuite currently trips on.
    2014-05-28  Pedro Alves  <>
    	* cp-demangle.c (d_dump): Handle DEMANGLE_COMPONENT_FUNCTION_PARAM
    	and DEMANGLE_COMPONENT_NUMBER.;h=6e933ccc75f683a19dda3c92c6d9a35f857b98b3

commit 6e933ccc75f683a19dda3c92c6d9a35f857b98b3
Author: Thomas Schwinge <>
Date:   Wed May 28 23:06:43 2014 +0100

    Fix test in libiberty/testsuite/demangle-expected.
    	* testsuite/demangle-expected: Fix last commit.
    git-svn-id: svn+ssh:// 138bc75d-0d04-0410-961f-82ee72b054a4;h=0aaa9a3aa1e68d309a4746633494b9a01a0575f5

commit 0aaa9a3aa1e68d309a4746633494b9a01a0575f5
Author: Andrew Burgess <>
Date:   Wed May 28 23:06:43 2014 +0100

    cplus-demangler, free resource after a failed call to gnu_special.
    2014-05-14  Andrew Burgess  <>
    	* cplus-dmem.c (internal_cplus_demangle): Free any resources
    	allocated by possible previous call to gnu_special.
    	(squangle_mop_up): Reset pointers to NULL after calling free.
    	* testsuite/demangle-expected: New test case.
    git-svn-id: svn+ssh:// 138bc75d-0d04-0410-961f-82ee72b054a4


Summary of changes:
 libiberty/ChangeLog                   |   16 ++++++++++++++++
 libiberty/cp-demangle.c               |    6 ++++++
 libiberty/cplus-dem.c                 |    7 +++++++
 libiberty/testsuite/demangle-expected |    5 +++++
 4 files changed, 34 insertions(+), 0 deletions(-)

gdb and binutils

                 reply	other threads:[~2014-05-28 22:08 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be 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).