public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
* [Bug translator/12221] New: Include build-ids in the script hash
@ 2010-11-15 22:59 jistone at redhat dot com
  2010-11-15 23:20 ` [Bug translator/12221] " mjw at redhat dot com
                   ` (2 more replies)
  0 siblings, 3 replies; 5+ messages in thread
From: jistone at redhat dot com @ 2010-11-15 22:59 UTC (permalink / raw)
  To: systemtap

http://sourceware.org/bugzilla/show_bug.cgi?id=12221

           Summary: Include build-ids in the script hash
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: translator
        AssignedTo: systemtap@sources.redhat.com
        ReportedBy: jistone@redhat.com


Now that PR9937 is done, I'm seeing some testsuite failures where the runtime
fails due to mismatched userspace build-ids.  In a few cases, we get binaries
that are similar enough that our probe addresses and such are the same, so our
caching reuses the ko, but the build-ids are actually different.  If we can
include the build-id in the script's hash, this should be resolved.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 5+ messages in thread
[parent not found: <bug-12221-6586@http.sourceware.org/bugzilla/>]

end of thread, other threads:[~2011-08-30 14:59 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-11-15 22:59 [Bug translator/12221] New: Include build-ids in the script hash jistone at redhat dot com
2010-11-15 23:20 ` [Bug translator/12221] " mjw at redhat dot com
2010-11-16  0:13 ` jistone at redhat dot com
2010-11-16  2:26 ` jistone at redhat dot com
     [not found] <bug-12221-6586@http.sourceware.org/bugzilla/>
2011-08-30 14:59 ` cmeek at redhat dot com

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).