From: Sterling Augustine <saugustine@google.com>
To: gdb-patches@sourceware.org
Subject: [Patch]: Allow dump memory command to dump more than 2GB
Date: Tue, 26 Jul 2011 19:53:00 -0000 [thread overview]
Message-ID: <CAEG7qUxhgMEm5Bf5J1X4oysHXGtwb-EaNqVB1GLyxLaycehh5A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 380 bytes --]
Hi All,
The enclosed, basically trivial, patch allows the dump memory command
to dump more than 2GB. It works simply by changing the parameter type
to match the declared type of the caller's argument.
Thanks,
Sterling
2011-07-26 Sterling Augustine <saugustine@google.com>
* cli/cli-dump.c (dump_binary_file): Change paramter type to ULONGEST.
(dump_bfd_file): Likewise.
[-- Attachment #2: dump_large.patch --]
[-- Type: text/x-patch, Size: 735 bytes --]
Index: cli-dump.c
===================================================================
RCS file: /cvs/src/src/gdb/cli/cli-dump.c,v
retrieving revision 1.44
diff -d -u -r1.44 cli-dump.c
--- cli-dump.c 3 Jun 2011 23:47:46 -0000 1.44
+++ cli-dump.c 26 Jul 2011 19:24:46 -0000
@@ -174,7 +174,7 @@
static void
dump_binary_file (const char *filename, const char *mode,
- const bfd_byte *buf, int len)
+ const bfd_byte *buf, ULONGEST len)
{
FILE *file;
int status;
@@ -188,7 +188,7 @@
static void
dump_bfd_file (const char *filename, const char *mode,
const char *target, CORE_ADDR vaddr,
- const bfd_byte *buf, int len)
+ const bfd_byte *buf, ULONGEST len)
{
bfd *obfd;
asection *osection;
next reply other threads:[~2011-07-26 19:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 19:53 Sterling Augustine [this message]
2011-07-26 21:12 ` Tom Tromey
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=CAEG7qUxhgMEm5Bf5J1X4oysHXGtwb-EaNqVB1GLyxLaycehh5A@mail.gmail.com \
--to=saugustine@google.com \
--cc=gdb-patches@sourceware.org \
/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