From: Jim Blandy <jimb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: PATCH: pass proper arguments to register_size
Date: Sat, 05 Jun 2004 03:30:00 -0000 [thread overview]
Message-ID: <vt2k6ymk7ft.fsf@zenia.home> (raw)
Committed as obvious.
2004-06-04 Jim Blandy <jimb@redhat.com>
* ppc-linux-nat.c (fetch_register): Don't forget to pass the
gdbarch argument to register_size.
Index: gdb/ppc-linux-nat.c
===================================================================
RCS file: /cvs/src/src/gdb/ppc-linux-nat.c,v
retrieving revision 1.43
diff -c -p -r1.43 ppc-linux-nat.c
*** gdb/ppc-linux-nat.c 4 Jun 2004 23:07:28 -0000 1.43
--- gdb/ppc-linux-nat.c 5 Jun 2004 03:24:16 -0000
*************** fetch_register (int tid, int regno)
*** 240,246 ****
32-bit platform, 64-bit floating-point registers will require two
transfers. */
for (bytes_transferred = 0;
! bytes_transferred < register_size (regno);
bytes_transferred += sizeof (PTRACE_XFER_TYPE))
{
errno = 0;
--- 240,246 ----
32-bit platform, 64-bit floating-point registers will require two
transfers. */
for (bytes_transferred = 0;
! bytes_transferred < register_size (current_gdbarch, regno);
bytes_transferred += sizeof (PTRACE_XFER_TYPE))
{
errno = 0;
reply other threads:[~2004-06-05 3:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=vt2k6ymk7ft.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=gdb-patches@sources.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