public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/20672] @defined(@cast()) regression
Date: Thu, 26 Jan 2017 13:18:00 -0000	[thread overview]
Message-ID: <bug-20672-6586-tUTI9ESnOk@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-20672-6586@http.sourceware.org/bugzilla/>

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

Frank Ch. Eigler <fche at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dsmith at redhat dot com

--- Comment #5 from Frank Ch. Eigler <fche at redhat dot com> ---
This appears to be fixed in commit f90352b.
It was caused by interesting infinite recursion of the python
variable-expander in-place mapping 

$var3
to
python2_get_var_obj(Py2Object_Repr($arg3, "arg3"))

and then the nested $arg3 ad infinitum.

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

      parent reply	other threads:[~2017-01-26 13:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-07 13:30 [Bug translator/20672] New: buildok/dentry-embedded.stp regression mcermak at redhat dot com
2017-01-06 12:44 ` [Bug translator/20672] @defined(@cast()) regression mcermak at redhat dot com
2017-01-20 20:55 ` fche at redhat dot com
2017-01-25 15:53 ` fche at redhat dot com
2017-01-26  4:27 ` penguin-kernel@i-love.sakura.ne.jp
2017-01-26 13:18 ` fche at redhat dot com [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=bug-20672-6586-tUTI9ESnOk@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).