From: "mcermak at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/17706] New: user string copy fault on s390 in 31-on-64 mode
Date: Fri, 12 Dec 2014 17:44:00 -0000 [thread overview]
Message-ID: <bug-17706-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=17706
Bug ID: 17706
Summary: user string copy fault on s390 in 31-on-64 mode
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: mcermak at redhat dot com
I see following user string copy fault on s390 in 31-on-64 mode. Note that
strace seems to have similar issue:
7.1 S s390x # cat openclose.c
/* COVERAGE: open openat close creat */
#define _GNU_SOURCE
#include <stdio.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <stdlib.h>
#include <unistd.h>
int main()
{
int fd1;
fd1 = openat(AT_FDCWD, "foobar2", O_WRONLY|O_CREAT, S_IRWXU);
close(fd1);
return 0;
}
7.1 S s390x # gcc openclose.c -m31
7.1 S s390x # stap -e 'probe syscall.openat {print(user_string($filename))}'
-c ./a.out
ERROR: user string copy fault -14 at 000002aa004006a0 [man error::fault] near
identifier 'user_string_n' at
/root/mcermak-systemtap/systemtap-build/share/systemtap/tapset/uconversions.stp:120:10
WARNING: Number of errors: 1, skipped probes: 1
WARNING: /root/mcermak-systemtap/systemtap-build/bin/staprun exited with
status: 1
Pass 5: run failed. [man error::pass5]
7.1 S s390x #
Please, review.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2014-12-12 17:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 17:44 mcermak at redhat dot com [this message]
2014-12-12 17:46 ` [Bug runtime/17706] " mcermak at redhat dot com
2014-12-12 19: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-17706-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).