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: Thu, 08 Sep 2016 15:24:00 -0000 [thread overview]
Message-ID: <bug-20557-6586-i2rmZGpknG@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 #11 from David Smith <dsmith at redhat dot com> ---
(In reply to SteveTsai from comment #10)
> Steve(In reply to David Smith from comment #9)
> >
> > Let's try something simple and get the udp and tcp tapsets out of the
> > picture. Try the following (which is what flightrec2.exp runs):
> >
> > # stap -F -o f.out -S 1,3 -e 'probe timer.ms(10) { for (j = 0; j < 1000;
> > j++) printf("1234567890\n") }'
> >
> > If that just creates 1 big file instead of 3 little ones that rotate, we'll
> > have to go deeper.
>
> # uname -a
> Linux steve-systemtap 4.4.0-34-generic #53~14.04.1-Ubuntu SMP Wed Jul 27
> 16:56:40 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
>
> I tried your example. It produce only one big file.
Something odd is going on then. Here's where we dig deeper. Run the following
commands:
# stap -p4 -m renamemod -F -o f.out -S 1,3 -e 'probe timer.ms(10) { for (j = 0;
j < 1000; j++) printf("1234567890\n") } probe timer.sec(5) { exit() }'
# sudo strace -f -ff -o strace.out /usr/local/bin/staprun -o f.out -R -S 1,3
renamemod.ko
If you are running the version of systemtap that came with Ubuntu, you'd change
the last command to:
# sudo strace -f -ff -o strace.out /usr/bin/staprun -o f.out -R -S 1,3
renamemod.ko
That should probably produce around 5 strace.out.PID files. Please attach those
to this bug. When I look for references to f.out.* files in my strace.out.*
files, I see the following:
# egrep 'f.out.[0-9]' strace.out.*
strace.out.29488:open("/home/dsmith/f.out.0",
O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE|O_CLOEXEC, 0666) = 6
strace.out.29491:open("/home/dsmith/f.out.1",
O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE|O_CLOEXEC, 0666) = 6
strace.out.29491:open("/home/dsmith/f.out.2",
O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE|O_CLOEXEC, 0666) = 6
strace.out.29491:unlink("/home/dsmith/f.out.0") = 0
strace.out.29491:open("/home/dsmith/f.out.3",
O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE|O_CLOEXEC, 0666) = 6
strace.out.29491:unlink("/home/dsmith/f.out.1") = 0
strace.out.29491:open("/home/dsmith/f.out.4",
O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE|O_CLOEXEC, 0666) = 6
strace.out.29491:unlink("/home/dsmith/f.out.2") = 0
strace.out.29491:open("/home/dsmith/f.out.5",
O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE|O_CLOEXEC, 0666) = 6
One possibility here might be that opening of 'f.out.1' is failing somehow for
you, so stap keeps writing to 'f.out.0'.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2016-09-08 15:24 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 [this message]
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
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-i2rmZGpknG@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).