Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH c++] Change some void* to gdb_byte*
Date: Fri, 09 Oct 2015 14:07:00 -0000	[thread overview]
Message-ID: <5617CA22.7060104@redhat.com> (raw)
In-Reply-To: <5617BCAF.8070704@ericsson.com>

On 10/09/2015 02:10 PM, Simon Marchi wrote:
> On 15-10-09 05:53 AM, Pedro Alves wrote:
>> This will need a fix similar to 39086a0e13:
>>   https://sourceware.org/ml/gdb-patches/2013-03/msg00449.html
> 
> Good find! Here is the updated version.  Only py-inferior.c changed.  I also
> noticed that infpy_write_memory needed the same change, I don't know why I
> didn't include it in the original patch.

LGTM.

Thanks,
Pedro Alves


  reply	other threads:[~2015-10-09 14:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-08 21:54 Simon Marchi
2015-10-09  9:53 ` Pedro Alves
2015-10-09 13:10   ` Simon Marchi
2015-10-09 14:07     ` Pedro Alves [this message]
2015-10-09 14:09       ` Simon Marchi

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=5617CA22.7060104@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@ericsson.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