From: Tom Tromey <tromey@redhat.com>
To: Sterling Augustine <saugustine@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [Patch]: Allow dump memory command to dump more than 2GB
Date: Tue, 26 Jul 2011 21:12:00 -0000 [thread overview]
Message-ID: <m37h74q08d.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAEG7qUxhgMEm5Bf5J1X4oysHXGtwb-EaNqVB1GLyxLaycehh5A@mail.gmail.com> (Sterling Augustine's message of "Tue, 26 Jul 2011 12:30:49 -0700")
>>>>> "Sterling" == Sterling Augustine <saugustine@google.com> writes:
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.
Tom
next prev parent reply other threads:[~2011-07-26 20:02 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 [this message]
2011-07-27 1:29 ` Paul Pluzhnikov
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=m37h74q08d.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=saugustine@google.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