public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/9907] gdb 6.8.50.20090225-cvs segfault in g++ demangler
Date: Tue, 27 May 2014 12:42:00 -0000	[thread overview]
Message-ID: <bug-9907-4717-VFJBV90x2z@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-9907-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=9907

Pedro Alves <palves at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |palves at redhat dot com
         Resolution|---                         |FIXED
   Target Milestone|6.8                         |7.0

--- Comment #8 from Pedro Alves <palves at redhat dot com> ---
I tried that on current mainline, and saw no crash.  The current gdb code has
been made to match libiberty a few years ago, between 6.8/7.0:

commit 71c25deab3d61e4cfbaffc7006704a27d1bc0737
Author: Tom Tromey <tromey@redhat.com>
Date:   Tue Mar 31 20:21:08 2009 +0000

    2009-03-31  Daniel Jacobowitz  <dan@codesourcery.com>
            Keith Seitz  <keiths@redhat.com>
            Jan Kratochvil  <jan.kratochvil@redhat.com>

        PR gdb/6817
...
        * cp-name-parser.y: operator() requires two parameters,
        according to libiberty.
...

Closing.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


       reply	other threads:[~2014-05-27 12:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-9907-4717@http.sourceware.org/bugzilla/>
2014-05-27 12:42 ` palves at redhat dot com [this message]
2009-02-26  5:26 [Bug corefiles/9907] New: gdb 6.8.50.20090225-cvs crashed while reading coredump ich at az2000 dot de
2009-03-11 16:34 ` [Bug gdb/9907] gdb 6.8.50.20090225-cvs segfault in g++ demangler francois dot rigault at amadeus dot com
2009-03-11 16:43 ` francois dot rigault at amadeus dot com
2009-03-12  9:41 ` francois dot rigault at amadeus dot com
2009-03-12 15:09 ` francois dot rigault at amadeus dot com
2009-03-12 15:14 ` ich at az2000 dot de
2009-03-12 21:09 ` tromey at redhat dot com
2009-03-16 16:52 ` francois dot rigault at amadeus dot com
2009-03-17  8:27 ` francois dot rigault at amadeus dot com

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=bug-9907-4717-VFJBV90x2z@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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: 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).