From: Pedro Alves <palves@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/3] Fix "Remote 'g' packet reply is too long" problems with multiple inferiors
Date: Tue, 03 Oct 2017 12:21:00 -0000 [thread overview]
Message-ID: <2370cfd3-d54a-9b86-fde4-0bdd8c10e5b3@redhat.com> (raw)
In-Reply-To: <867ewc793g.fsf@gmail.com>
On 10/03/2017 12:40 PM, Yao Qi wrote:
> Pedro Alves <palves@redhat.com> writes:
>
>> struct gdbarch *
>> default_thread_architecture (struct target_ops *ops, ptid_t ptid)
>> {
>> - return target_gdbarch ();
>> + inferior *inf = find_inferior_ptid (ptid);
>> + gdb_assert (inf != NULL);
>> + return inf->gdbarch;
>> }
>
> It is right, but forgot to mention that we need to update
> spu_thread_architecture too,
>
> if (parse_spufs_run (ptid, &spufs_fd, &spufs_addr))
> return spu_gdbarch (spufs_fd);
>
> return target_gdbarch ();
>
> it looks wrong to call target_gdbarch. We may need to replace
> target_gdbarch with default_thread_architecture.
I think you're right.
The target_gdbarch reference in process_stop_reply looks incorrect
as well (last hunk below). I'm current running test with the patch below
on top. Kind of curious that I didn't run into this one before.
From 60956bf76cf0b5582f4085f8f36f1ee0bf7f804f Mon Sep 17 00:00:00 2001
From: Pedro Alves <palves@redhat.com>
Date: Mon, 2 Oct 2017 18:23:10 +0100
Subject: [PATCH] more target_gdbarch
---
gdb/remote.c | 18 ++++++++++--------
1 file changed, 10 insertions(+), 8 deletions(-)
diff --git a/gdb/remote.c b/gdb/remote.c
index b6a81a2..894c3de 100644
--- a/gdb/remote.c
+++ b/gdb/remote.c
@@ -6363,6 +6363,9 @@ typedef struct stop_reply
struct target_waitstatus ws;
+ /* The architecture associated with the expedited registers. */
+ gdbarch *arch;
+
/* Expedited registers. This makes remote debugging a bit more
efficient for those targets that provide critical registers as
part of their normal status mechanism (as another roundtrip to
@@ -6838,7 +6841,6 @@ static void
remote_parse_stop_reply (char *buf, struct stop_reply *event)
{
remote_arch_state *rsa = NULL;
- struct gdbarch *reply_arch = NULL;
ULONGEST addr;
const char *p;
int skipregs = 0;
@@ -7048,11 +7050,11 @@ Packet: '%s'\n"),
continue;
}
- reply_arch = inf->gdbarch;
- rsa = get_remote_arch_state (reply_arch);
+ event->arch = inf->gdbarch;
+ rsa = get_remote_arch_state (event->arch);
}
- struct packet_reg *reg = packet_reg_from_pnum (reply_arch,
+ struct packet_reg *reg = packet_reg_from_pnum (event->arch,
rsa, pnum);
cached_reg_t cached_reg;
@@ -7063,13 +7065,13 @@ Packet: '%s'\n"),
cached_reg.num = reg->regnum;
cached_reg.data = (gdb_byte *)
- xmalloc (register_size (reply_arch, reg->regnum));
+ xmalloc (register_size (event->arch, reg->regnum));
p = p1 + 1;
fieldsize = hex2bin (p, cached_reg.data,
- register_size (reply_arch, reg->regnum));
+ register_size (event->arch, reg->regnum));
p += 2 * fieldsize;
- if (fieldsize < register_size (reply_arch, reg->regnum))
+ if (fieldsize < register_size (event->arch, reg->regnum))
warning (_("Remote reply is too short: %s"), buf);
VEC_safe_push (cached_reg_t, event->regcache, &cached_reg);
@@ -7285,7 +7287,7 @@ process_stop_reply (struct stop_reply *stop_reply,
if (stop_reply->regcache)
{
struct regcache *regcache
- = get_thread_arch_regcache (ptid, target_gdbarch ());
+ = get_thread_arch_regcache (ptid, stop_reply->arch);
cached_reg_t *reg;
int ix;
--
2.5.5
next prev parent reply other threads:[~2017-10-03 12:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 15:15 [PATCH 0/3] " Pedro Alves
2017-10-02 15:15 ` [PATCH 1/3] Redesign mock environment for gdbarch selftests Pedro Alves
2017-10-03 11:06 ` Yao Qi
2017-10-03 12:05 ` Pedro Alves
2017-10-04 10:39 ` Yao Qi
2017-10-02 15:15 ` [PATCH 3/3] Fix "Remote 'g' packet reply is too long" problems with multiple inferiors Pedro Alves
2017-10-03 11:36 ` Yao Qi
2017-10-03 11:40 ` Yao Qi
2017-10-03 12:21 ` Pedro Alves [this message]
2017-10-03 14:02 ` Pedro Alves
2017-10-04 10:21 ` Yao Qi
2017-10-04 17:38 ` Pedro Alves
2017-10-05 16:50 ` Ulrich Weigand
2017-10-05 17:08 ` Pedro Alves
2017-12-12 21:33 ` Maciej W. Rozycki
2017-12-13 0:45 ` Pedro Alves
2017-12-13 11:31 ` Maciej W. Rozycki
2017-10-02 15:15 ` [PATCH 2/3] Reimplement support for "maint print registers" with no running inferior yet Pedro Alves
2017-10-03 11:17 ` Yao Qi
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=2370cfd3-d54a-9b86-fde4-0bdd8c10e5b3@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.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