public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "jlebon at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/16165] @perf operator in error msgs is corrupted
Date: Wed, 13 Nov 2013 15:53:00 -0000	[thread overview]
Message-ID: <bug-16165-6586-Ec0OZTwrAm@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16165-6586@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=16165

--- Comment #3 from Jonathan Lebon <jlebon at redhat dot com> ---
This is due to the @perf operator getting expanded to the counter symbol (see
dwarf_var_expanding_visitor::visit_perf_op()). The issue is that the symbol's
token content is set to the literal value passed to the @perf operator.

What then happens is that when we try to color the offending token, the token's
content ('a') doesn't match the original source line ('@perf').

There are (at least) two possible ways to fix this:
Patch 1. Only color stuff whose contents would match exactly the source line.
Patch 2. Make sure the new token the expanded perf symbol uses has the original
content.

Not sure what's the right way. Patch 1 is more general in that other things of
this sort will not be colored. On the other hand, patch 2 allows the '@perf'
keyword to get colored, but I'm not entirely sure what other repercussions
replacing the content may have (and whether this is something done in other
places).

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2013-11-13 15:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-13 15:45 [Bug translator/16165] New: " jlebon at redhat dot com
2013-11-13 15:51 ` [Bug translator/16165] " jlebon at redhat dot com
2013-11-13 15:51 ` jlebon at redhat dot com
2013-11-13 15:53 ` jlebon at redhat dot com [this message]
2013-11-13 17:54 ` jistone at redhat dot com
2013-11-13 18:30 ` jlebon at redhat dot com
2013-11-13 22:36 ` jlebon at redhat dot com
2013-11-14 16:21 ` jlebon at redhat dot com
2013-11-14 16:54 ` jlebon at redhat dot com

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=bug-16165-6586-Ec0OZTwrAm@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).