Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Jim Blandy" <jimb@red-bean.com>
To: "Der Herr Hofrat" <der.herr@hofr.at>
Cc: gdb@sources.redhat.com
Subject: Re: tracepoint implementation question
Date: Sun, 19 Mar 2006 17:24:00 -0000	[thread overview]
Message-ID: <8f2776cb0603181046x6145eeblc856015b07d3dc91@mail.gmail.com> (raw)
In-Reply-To: <200603191024.k2JAOGh02932@hofr.at>

Actually, I think the problem you're running into is that the
debugging information in your executable is using Dwarf location
expressions to describe where the variables live, and the tracepoint
code isn't using the supplied functions to translate between Dwarf
location expressions and tracepoint bytecodes.

"Symbol class 21" is LOC_COMPUTED_ARG; the tracepoint code ought to be
calling the 'tracepoint_var_ref' function in the symbol's 'struct
symbol_ops' structure.  Probably we need a new function
gen_trace_for_symbol in ax-gdb.c, analogous to gen_trace_for_expr. 
Depending on the exact expression at hand, dwarf2_tracepoint_var_ref
may need to be expanded.

You're right, to some extent this indicates a lack of active
maintenance.  When the tracepoint code was written, few variables used
Dwarf expressions; now it is much more common.

Could you post the result of running 'readelf -wi' on your test
program (the one with 'someint' in it)?  (If the output is very large,
put it on the web and post a link.)


  reply	other threads:[~2006-03-18 18:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-18 11:19 Der Herr Hofrat
2006-03-19 17:24 ` Jim Blandy [this message]
2006-03-20  6:18   ` Der Herr Hofrat
2006-03-20  6:38     ` Jim Blandy

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=8f2776cb0603181046x6145eeblc856015b07d3dc91@mail.gmail.com \
    --to=jimb@red-bean.com \
    --cc=der.herr@hofr.at \
    --cc=gdb@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