public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "mcermak at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/18649] int_arg() misbehaves on x86[_64] for 32-bit uprobe in binary having debuginfo
Date: Mon, 31 Aug 2015 08:22:00 -0000	[thread overview]
Message-ID: <bug-18649-6586-haFyzQagQ9@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18649-6586@http.sourceware.org/bugzilla/>

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

--- Comment #14 from Martin Cermak <mcermak at redhat dot com> ---
Created attachment 8565
  --> https://sourceware.org/bugzilla/attachment.cgi?id=8565&action=edit
updated patch

(In reply to Josh Stone from comment #13)
> ENABLE_PROLOGUES is not quite right.  The former true/false values should
> now be always/auto to keep the same behavior -- there was no never.

Ouch, you are right.  Fixed.

> It appears you removed prologues from usage() entirely, instead of adding
> your new switch to the output.  Why?

Fixed.

> The manpage explanation of "auto" is odd: "enable only if possible"?  As if
> "always" will instead do the impossible? :)  The real logic behind auto is a
> heuristic for when we think it will be useful, in userspace with low quality
> location info.  Not sure of a short blurb  -- maybe just "enabled by
> heuristic".

:) Yup, updated. 

> The staprun.h change doesn't belong at all.  I assume that was copying
> color_mode, but prologues are only a concern to the translator.

Yes, I've been following Jonathan's color_mode implementation.  When looking
over the patch before attaching it, I felt this is somewhat weird, but
unfortunately left it there.  Fixed.

> Have you confirmed that --prologue-searching=never solves your original
> problem?

Sure.  I did that before and re-tested now again with attached updated patch.

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

  parent reply	other threads:[~2015-08-31  8:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09  9:29 [Bug tapsets/18649] New: " mcermak at redhat dot com
2015-07-09  9:32 ` [Bug tapsets/18649] " mcermak at redhat dot com
2015-07-09 15:50 ` jistone at redhat dot com
2015-07-10 20:45 ` mcermak at redhat dot com
2015-07-10 20:57 ` mcermak at redhat dot com
2015-07-10 21:47 ` jistone at redhat dot com
2015-07-13 14:38 ` dsmith at redhat dot com
2015-07-13 16:52 ` jistone at redhat dot com
2015-07-21 14:10 ` mcermak at redhat dot com
2015-07-29 16:29 ` mcermak at redhat dot com
2015-08-14 19:07 ` dsmith at redhat dot com
2015-08-21  7:49 ` mcermak at redhat dot com
2015-08-21 13:50 ` dsmith at redhat dot com
2015-08-21 17:42 ` jistone at redhat dot com
2015-08-31  8:22 ` mcermak at redhat dot com [this message]
2015-09-01  7:36 ` mcermak at redhat dot com
2015-09-04  7:47 ` mcermak 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-18649-6586-haFyzQagQ9@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).