From: Tom Tromey <tromey@redhat.com>
To: "Ulrich Weigand" <uweigand@de.ibm.com>
Cc: pedro@codesourcery.com (Pedro Alves),
gdb-patches@sourceware.org,
brobecker@adacore.com (Joel Brobecker)
Subject: FYI: tracepoints and multi-arch (Was: RFC: remove gdbarch from struct breakpoint)
Date: Mon, 14 Nov 2011 16:10:00 -0000 [thread overview]
Message-ID: <m3zkfyr8hf.fsf_-_@fleche.redhat.com> (raw)
In-Reply-To: <m3ipmuiizd.fsf@fleche.redhat.com> (Tom Tromey's message of "Tue, 08 Nov 2011 11:09:42 -0700")
Tom> If I do drop it, I will still pull in the tracepoint changes, since I
Tom> think those are probably good.
I am checking this in, as discussed.
This patch fixes a few spots where tracepoints rely on the breakpoint's
arch; in general I think the location's arch is more appropriate.
Tom
2011-11-14 Tom Tromey <tromey@redhat.com>
* tracepoint.c (encode_actions_1): Use the location's gdbarch.
(encode_actions): Likewise.
Index: tracepoint.c
===================================================================
RCS file: /cvs/src/src/gdb/tracepoint.c,v
retrieving revision 1.236
diff -u -r1.236 tracepoint.c
--- tracepoint.c 14 Nov 2011 15:18:54 -0000 1.236
+++ tracepoint.c 14 Nov 2011 16:07:57 -0000
@@ -1370,14 +1370,14 @@
if (0 == strncasecmp ("$reg", action_exp, 4))
{
- for (i = 0; i < gdbarch_num_regs (t->gdbarch); i++)
+ for (i = 0; i < gdbarch_num_regs (tloc->gdbarch); i++)
add_register (collect, i);
action_exp = strchr (action_exp, ','); /* more? */
}
else if (0 == strncasecmp ("$arg", action_exp, 4))
{
add_local_symbols (collect,
- t->gdbarch,
+ tloc->gdbarch,
tloc->address,
frame_reg,
frame_offset,
@@ -1387,7 +1387,7 @@
else if (0 == strncasecmp ("$loc", action_exp, 4))
{
add_local_symbols (collect,
- t->gdbarch,
+ tloc->gdbarch,
tloc->address,
frame_reg,
frame_offset,
@@ -1399,7 +1399,7 @@
struct cleanup *old_chain1 = NULL;
aexpr = gen_trace_for_return_address (tloc->address,
- t->gdbarch);
+ tloc->gdbarch);
old_chain1 = make_cleanup_free_agent_expr (aexpr);
@@ -1452,7 +1452,7 @@
{
const char *name = &exp->elts[2].string;
- i = user_reg_map_name_to_regnum (t->gdbarch,
+ i = user_reg_map_name_to_regnum (tloc->gdbarch,
name, strlen (name));
if (i == -1)
internal_error (__FILE__, __LINE__,
@@ -1475,7 +1475,7 @@
case OP_VAR_VALUE:
collect_symbol (collect,
exp->elts[2].symbol,
- t->gdbarch,
+ tloc->gdbarch,
frame_reg,
frame_offset,
tloc->address);
@@ -1588,8 +1588,8 @@
*tdp_actions = NULL;
*stepping_actions = NULL;
- gdbarch_virtual_frame_pointer (t->gdbarch,
- t->loc->address, &frame_reg, &frame_offset);
+ gdbarch_virtual_frame_pointer (tloc->gdbarch,
+ tloc->address, &frame_reg, &frame_offset);
actions = breakpoint_commands (t);
prev parent reply other threads:[~2011-11-14 16:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 15:21 RFC: remove gdbarch from struct breakpoint Tom Tromey
2011-11-07 15:21 ` Joel Brobecker
2011-11-07 16:10 ` Pedro Alves
2011-11-07 16:52 ` Stan Shebs
2011-11-08 16:22 ` Ulrich Weigand
2011-11-08 17:00 ` Tom Tromey
2011-11-08 17:19 ` Ulrich Weigand
2011-11-08 18:10 ` Tom Tromey
2011-11-09 18:22 ` Tom Tromey
2011-11-14 16:10 ` Tom Tromey [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=m3zkfyr8hf.fsf_-_@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=uweigand@de.ibm.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