public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ppluzhnikov at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/12528] Should we handle constructors that are garbage collected but their debug info isn't?
Date: Wed, 16 Mar 2011 18:22:00 -0000	[thread overview]
Message-ID: <bug-12528-4717-OvBtO5dLgl@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12528-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=12528

Paul Pluzhnikov <ppluzhnikov at google dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #4 from Paul Pluzhnikov <ppluzhnikov at google dot com> 2011-03-16 18:22:29 UTC ---
Verified original test case is fixed as well.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2011-03-16 18:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-01 22:18 [Bug breakpoints/12528] New: " dje at google dot com
2011-03-11  8:12 ` [Bug breakpoints/12528] " dje at google dot com
2011-03-16 18:15 ` cvs-commit at gcc dot gnu.org
2011-03-16 18:16 ` cvs-commit at gcc dot gnu.org
2011-03-16 18:22 ` ppluzhnikov at google dot com [this message]
2014-09-19  8:59 ` cvs-commit at gcc dot gnu.org

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-12528-4717-OvBtO5dLgl@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).