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 server/20557] It seems like that switching output file doesn't work.
Date: Fri, 09 Sep 2016 13:45:00 -0000	[thread overview]
Message-ID: <bug-20557-6586-8nfGYZE6dv@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-20557-6586@http.sourceware.org/bugzilla/>

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

--- Comment #18 from David Smith <dsmith at redhat dot com> ---
After looking at the strace files you attached, I'm quite confused:

====
# grep f.out strace.out.*
strace.out.29045:execve("/usr/bin/staprun", ["/usr/bin/staprun", "-o", "f.out",
"-R", "-S", "1,3", "renamemod.ko"], [/* 20 vars */]) = 0
strace.out.29045:execve("/usr/lib/systemtap/stapio",
["/usr/lib/systemtap/stapio", "-o", "f.out", "-R", "-S", "1,3", "ren_29045",
"-F3"], [/* 20 vars */]) = 0
strace.out.29045:open("/root/systemtap/examples/f.out.0",
O_WRONLY|O_CREAT|O_TRUNC, 0666) = 6
strace.out.29048:open("/root/systemtap/examples/f.out.1",
O_WRONLY|O_CREAT|O_TRUNC, 0666) = 6
strace.out.29048:open("/root/systemtap/examples/f.out.2",
O_WRONLY|O_CREAT|O_TRUNC, 0666) = 6
strace.out.29048:unlink("/root/systemtap/examples/f.out.0") = 0
strace.out.29048:open("/root/systemtap/examples/f.out.3",
O_WRONLY|O_CREAT|O_TRUNC, 0666) = 6
strace.out.29048:unlink("/root/systemtap/examples/f.out.1") = 0
strace.out.29048:open("/root/systemtap/examples/f.out.4",
O_WRONLY|O_CREAT|O_TRUNC, 0666) = 6
strace.out.29048:unlink("/root/systemtap/examples/f.out.2") = 0
strace.out.29048:open("/root/systemtap/examples/f.out.5",
O_WRONLY|O_CREAT|O_TRUNC, 0666) = 6
====

That strace output clearly shows systemtap creating f.out.0, f.out.1, f.out.2,
unlinking f.out.0, creating f.out.3, unlinking f.out.1, creating f.out.4,
unlinking f.out.2, and creating f.out.5. All the open() and unlink() syscalls
succeed.

At this point I'm not sure what is going on with your system. Perhaps you
should try running systemtap again in an empty directory?

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

  parent reply	other threads:[~2016-09-09 13:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-06  3:05 [Bug server/20557] New: " steve.tsai at nexusguard dot com
2016-09-06  5:46 ` [Bug server/20557] " steve.tsai at nexusguard dot com
2016-09-06 18:31 ` dsmith at redhat dot com
2016-09-06 18:51 ` dsmith at redhat dot com
2016-09-06 19:38 ` dsmith at redhat dot com
2016-09-07  2:46 ` steve.tsai at nexusguard dot com
2016-09-07  2:49 ` steve.tsai at nexusguard dot com
2016-09-07  2:49 ` steve.tsai at nexusguard dot com
2016-09-07 14:17 ` dsmith at redhat dot com
2016-09-07 20:23 ` dsmith at redhat dot com
2016-09-08  2:04 ` steve.tsai at nexusguard dot com
2016-09-08 15:24 ` dsmith at redhat dot com
2016-09-09  2:16 ` steve.tsai at nexusguard dot com
2016-09-09  2:16 ` steve.tsai at nexusguard dot com
2016-09-09  2:19 ` steve.tsai at nexusguard dot com
2016-09-09  2:20 ` steve.tsai at nexusguard dot com
2016-09-09  2:20 ` steve.tsai at nexusguard dot com
2016-09-09  2:21 ` steve.tsai at nexusguard dot com
2016-09-09 13:45 ` dsmith at redhat dot com [this message]
2024-02-21 13:26 ` fche 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-20557-6586-8nfGYZE6dv@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).