Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@red-bean.com>
To: Randolph Chung <randolph@tausq.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/RFC] Support DW_OP_breg for tracepoints
Date: Mon, 14 Nov 2005 02:27:00 -0000	[thread overview]
Message-ID: <8f2776cb0511131539j17ae5144n87b1aedab1fa420e@mail.gmail.com> (raw)
In-Reply-To: <43775DDB.6020408@tausq.org>

On 11/13/05, Randolph Chung <randolph@tausq.org> wrote:
> Warning: I don't really understand how this works :-)
>
> On hppa-linux, when running gdb.trace/save-trace.exp, the test fails
> because of:
>
> "Unsupported DWARF opcode in the location of q1"
>
> The opcode in question is "DW_OP_breg3". The attached patch attempts to
> add support for DW_OP_breg0..DW_OP_breg31. With this patch hppa-linux
> passes the testcase, although not really understanding DWARF-2 I am not
> certain this is 100% correct. DWARF experts, comments appreciated.

Why are you adding the offset twice?  Is it just cut-and-paste from
the DW_OP_fbreg code?  That looks wrong, too.

This code should go in ax-gdb.[ch].  That has a translator from GDB
expressions to agent expressions; it would make sense to also have a
translator from Dwarf expressions to agent expressions.


  parent reply	other threads:[~2005-11-13 23:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-13 18:10 Randolph Chung
2005-11-13 18:11 ` Daniel Jacobowitz
2005-11-14  2:27 ` Jim Blandy [this message]
2005-11-14  3:41   ` Randolph Chung
2005-11-14  3:56     ` Daniel Jacobowitz
2005-11-14 15:57       ` Jim Blandy
2005-11-19 19:41       ` Randolph Chung

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=8f2776cb0511131539j17ae5144n87b1aedab1fa420e@mail.gmail.com \
    --to=jimb@red-bean.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=randolph@tausq.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