Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Martin Galvan <martin.galvan@tallertechnologies.com>
To: Luis Machado <lgustavo@codesourcery.com>
Cc: gdb-patches <gdb-patches@sourceware.org>,
	Pedro Alves <palves@redhat.com>
Subject: Re: [PATCH v3] Fix gdb crash when trying to print the address of a synthetic C++ reference
Date: Mon, 11 Apr 2016 21:45:00 -0000	[thread overview]
Message-ID: <CAOKbPbZCudQFrmUhM8jJHBiuzrhXZ_3PnT9vmG5NjFFDD+SrGQ@mail.gmail.com> (raw)
In-Reply-To: <570C1723.20908@codesourcery.com>

On Mon, Apr 11, 2016 at 6:29 PM, Luis Machado <lgustavo@codesourcery.com> wrote:
> Did it work or should we not expect a v4?

Sorry, I decided against using it and sent a 'PING' for v3 instead.
Here's the new thread, which includes the rationale for not using it:

https://sourceware.org/ml/gdb-patches/2016-04/msg00188.html


      reply	other threads:[~2016-04-11 21:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-01 21:21 Martin Galvan
     [not found] ` <1459776273-3434-1-git-send-email-martin.galvan@tallertechnologies.com>
2016-04-04 19:54   ` Martin Galvan
2016-04-11 21:29     ` Luis Machado
2016-04-11 21:45       ` Martin Galvan [this message]

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=CAOKbPbZCudQFrmUhM8jJHBiuzrhXZ_3PnT9vmG5NjFFDD+SrGQ@mail.gmail.com \
    --to=martin.galvan@tallertechnologies.com \
    --cc=gdb-patches@sourceware.org \
    --cc=lgustavo@codesourcery.com \
    --cc=palves@redhat.com \
    /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