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 runtime/18213] New: on arm, the runtime doesn't return correct syscall numbers
Date: Wed, 08 Apr 2015 17:00:00 -0000	[thread overview]
Message-ID: <bug-18213-6586@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 18213
           Summary: on arm, the runtime doesn't return correct syscall
                    numbers
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
          Assignee: systemtap at sourceware dot org
          Reporter: dsmith at redhat dot com
              Host: arm

On arm (3.19.3-200.fc21.armv7hl), we're getting a large number of failures in
the syscall/nd_syscall tapset testsuite:

====
# of expected passes            66
# of unexpected failures        200
====

Lots of these are related to dwarfless-probe argument problems, but even in the
dwarf probe case the numbers are much worse than they should be.

After some debugging, I found out that the _stp_syscall_nr() tapset function
always returns 0, which breaks all use of the syscall gate macros (that prevent
syscall nesting). It appears that the kernel version of syscall_get_nr() always
returns 0 on arm.

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

             reply	other threads:[~2015-04-08 17:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08 17:00 dsmith at redhat dot com [this message]
2015-04-08 17:03 ` [Bug runtime/18213] " dsmith 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-18213-6586@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).