From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Sterling Augustine <saugustine@google.com>, gdb-patches@sourceware.org
Subject: Re: [Patch]: Allow dump memory command to dump more than 2GB
Date: Wed, 27 Jul 2011 01:29:00 -0000 [thread overview]
Message-ID: <CALoOobOwp=zDqXg9bto24dn0RHaZym7k6OgUmh=QRRR686mTNw@mail.gmail.com> (raw)
In-Reply-To: <m37h74q08d.fsf@fleche.redhat.com>
On Tue, Jul 26, 2011 at 1:02 PM, Tom Tromey <tromey@redhat.com> wrote:
>
> Sterling> 2011-07-26 Sterling Augustine <saugustine@google.com>
> Sterling> * cli/cli-dump.c (dump_binary_file): Change paramter type to ULONGEST.
> Sterling> (dump_bfd_file): Likewise.
>
> Ok.
I've committed this patch for Sterling.
Thanks,
--
Paul Pluzhnikov
prev parent reply other threads:[~2011-07-26 21:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 19:53 Sterling Augustine
2011-07-26 21:12 ` Tom Tromey
2011-07-27 1:29 ` Paul Pluzhnikov [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='CALoOobOwp=zDqXg9bto24dn0RHaZym7k6OgUmh=QRRR686mTNw@mail.gmail.com' \
--to=ppluzhnikov@google.com \
--cc=gdb-patches@sourceware.org \
--cc=saugustine@google.com \
--cc=tromey@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