public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/15219] syscall.exp failures on RHEL5, RHEL6, and rawhide
Date: Tue, 07 Jan 2014 22:02:00 -0000	[thread overview]
Message-ID: <bug-15219-6586-nn6b4LMoyE@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15219-6586@http.sourceware.org/bugzilla/>

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

David Smith <dsmith at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #13 from David Smith <dsmith at redhat dot com> ---
(In reply to David Smith from comment #12)
> Created attachment 7262 [details]
> simpler patch
> 
> Here's a simpler version of the last patch that just fixes one syscall.exp
> failure for the 32-bit 'clock' subtest when run on rawhide x86_64. This
> simpler patch should make this approach easier to review and understand.
> 
> Note that we'd have to make similar changes to nd_syscalls.stp.
> 
> Also, it might make sense to combine the syscall.clock_nanosleep and
> syscall.compat_clock_settime probe aliases with their 'compat' probe aliases.

I've made changes to the syscall tapsets to implement this idea. At this point,
the syscall.exp and nd_syscall.exp testcases pass on every platform I've tested
on.

(Note that these changes don't really fix *all* nested syscall problems, just
the ones tested by the testsuite. To catch more failures, we'd need to expand
the testsuite.)

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

      parent reply	other threads:[~2014-01-07 22:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-01 17:54 [Bug tapsets/15219] New: " dsmith at redhat dot com
2013-03-04 17:54 ` [Bug tapsets/15219] " dsmith at redhat dot com
2013-03-04 18:40 ` fche at redhat dot com
2013-06-03 13:38 ` dsmith at redhat dot com
2013-06-04 15:14 ` fche at redhat dot com
2013-06-05 17:58 ` dsmith at redhat dot com
2013-06-06 18:03 ` dsmith at redhat dot com
2013-06-11 14:37 ` dsmith at redhat dot com
2013-06-17 16:10 ` dsmith at redhat dot com
2013-08-26 20:44 ` dsmith at redhat dot com
2013-10-08 18:03 ` dsmith at redhat dot com
2013-10-08 18:15 ` dsmith at redhat dot com
2013-10-31 17:24 ` dsmith at redhat dot com
2014-01-07 22:02 ` dsmith 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-15219-6586-nn6b4LMoyE@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).