From: Luis Machado <lgustavo@codesourcery.com>
To: Martin Galvan <martin.galvan@tallertechnologies.com>,
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:29:00 -0000 [thread overview]
Message-ID: <570C1723.20908@codesourcery.com> (raw)
In-Reply-To: <CAOKbPbYshoXWgbNyEjym-bO_ahGa1tFDij=XMibMgVePD6XwXA@mail.gmail.com>
On 04/04/2016 02:53 PM, Martin Galvan wrote:
> Looking back it seems that I could use readjust_indirect_value_type
> instead of manually setting the type and enclosing type of the new
> value. I'll give it a try and send a v4 if it works.
>
Did it work or should we not expect a v4?
next prev parent reply other threads:[~2016-04-11 21:29 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 [this message]
2016-04-11 21:45 ` Martin Galvan
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=570C1723.20908@codesourcery.com \
--to=lgustavo@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=martin.galvan@tallertechnologies.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