From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Siddhesh Poyarekar <siddhesh@redhat.com>
Cc: gdb-patches@sourceware.org, Tom Tromey <tromey@redhat.com>
Subject: [commit] [PATCH] Memory reads and writes should have size_t length
Date: Tue, 05 Jun 2012 21:23:00 -0000 [thread overview]
Message-ID: <20120605212300.GB31768@host2.jankratochvil.net> (raw)
In-Reply-To: <20120605084605.186d537a@spoyarek>
On Tue, 05 Jun 2012 05:16:05 +0200, Siddhesh Poyarekar wrote:
> OK, thanks for the explanation. Updated patch attached.
Checked in. (simplified ChangeLog)
tested on {x86_64,x86_64-m32}-fedora18pre-linux-gnu.
Thanks,
Jan
http://sourceware.org/ml/gdb-cvs/2012-06/msg00038.html
--- src/gdb/ChangeLog 2012/06/05 21:18:04 1.14328
+++ src/gdb/ChangeLog 2012/06/05 21:22:30 1.14329
@@ -1,3 +1,14 @@
+2012-06-05 Siddhesh Poyarekar <siddhesh@redhat.com>
+
+ * corefile.c (read_memory, read_stack, write_memory): Accept LEN
+ argument as ssize_t.
+ * gdbcore.h (read_memory, read_stack, write_memory): Likewise.
+ * remote.c (remote_write_bytes_aux, remote_write_bytes): Likewise.
+ * target.c (target_read_stack, target_write_memory)
+ (target_write_raw_memory): Likewise.
+ * target.h (target_read_stack, target_write_memory)
+ (target_write_raw_memory): Likewise.
+
2012-06-05 Jan Kratochvil <jan.kratochvil@redhat.com>
* symfile-mem.c: Change gdb_static_assert to ssize_t.
[patch is the same]
prev parent reply other threads:[~2012-06-05 21:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 8:08 Siddhesh Poyarekar
2012-06-01 18:10 ` Jan Kratochvil
2012-06-01 19:59 ` Siddhesh Poyarekar
2012-06-04 21:54 ` Jan Kratochvil
2012-06-05 3:16 ` Siddhesh Poyarekar
2012-06-05 21:21 ` [commit] Change target_read_memory size_t->ssize_t [Re: [PATCH] Memory reads and writes should have size_t length] Jan Kratochvil
2012-06-05 21:23 ` Jan Kratochvil [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=20120605212300.GB31768@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=siddhesh@redhat.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