From: "mcermak at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/18083] listing_mode.exp fails on rhel6
Date: Thu, 05 Mar 2015 10:35:00 -0000 [thread overview]
Message-ID: <bug-18083-6586-6npee6biNc@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18083-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18083
--- Comment #1 from Martin Cermak <mcermak at redhat dot com> ---
Created attachment 8169
--> https://sourceware.org/bugzilla/attachment.cgi?id=8169&action=edit
binary created using gcc-4.4.7-11.el6.x86_64
Attaching testing binary and verbose stap (version 2.8/0.161, commit
release-2.7-37-gf94683c76783 + changes) output:
=======
# stap -vvv -l 'process.function("main@listing_mode.c").label("main_label")'
-c ./listing_mode
... stuff deleted ...
parse 'main@listing_mode.c', func 'main', file 'listing_mode.c'
focused on module '/root/work/tmp.nsVLz0WYTh/listing_mode' =
[0x400000-0x600b60, bias 0 file /root/work/tmp.nsVLz0WYTh/listing_mode ELF
machine |x86_64 (code 62)
focused on module '/root/work/tmp.nsVLz0WYTh/listing_mode'
selected source file '/root/work/tmp.nsVLz0WYTh/listing_mode.c'
selected function main
searching for prologue of function 'main'
0x4006d2-0x400701@/root/work/tmp.nsVLz0WYTh/listing_mode.c:29
checking line record 0x4006d2@/root/work/tmp.nsVLz0WYTh/listing_mode.c:29
checking line record 0x4006d6@/root/work/tmp.nsVLz0WYTh/listing_mode.c:31
prologue found function 'main' = 0x4006d6
probe main@/root/work/tmp.nsVLz0WYTh/listing_mode.c:37
process=/root/work/tmp.nsVLz0WYTh/listing_mode reloc=.absolute pc=0x4006f4
Eliding side-effect-free empty block operator '{' at <input>:1:67
WARNING: side-effect-free probe 'probe_2652': keyword at <input>:1:1
source: probe process.function("main@listing_mode.c").label("main_label") {}
^
process("/root/work/tmp.nsVLz0WYTh/listing_mode").function("main@/root/work/tmp.nsVLz0WYTh/listing_mode.c:37")
/* pc=.absolute+0x4006f4 */ /* <-
process("/root/work/tmp.nsVLz0WYTh/listing_mode").function("main@/root/work/tmp.nsVLz0WYTh/listing_mode.c:37").label("main_label")
*/
chain[3]:
[0]:
locations[1]:
[0]:
process("/root/work/tmp.nsVLz0WYTh/listing_mode").function("main@/root/work/tmp.nsVLz0WYTh/listing_mode.c:37")
[1]:
locations[1]:
[0]:
process("/root/work/tmp.nsVLz0WYTh/listing_mode").function("main@/root/work/tmp.nsVLz0WYTh/listing_mode.c:37").label("main_label")
[2]:
locations[1]:
[0]:
process("./listing_mode").function("main@listing_mode.c").label("main_label")
process("/root/work/tmp.nsVLz0WYTh/listing_mode").function("main@/root/work/tmp.nsVLz0WYTh/listing_mode.c:37").label("main_label")
Pass 2: analyzed script: 1 probe(s), 0 function(s), 0 embed(s), 0 global(s)
using 207372virt/36008res/3828shr/32420data kb, in 0usr/10sys/8real ms.
Running rm -rf /tmp/stapYVnhGR
Spawn waitpid result (0x0): 0
=======
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2015-03-05 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 10:28 [Bug runtime/18083] New: " mcermak at redhat dot com
2015-03-05 10:35 ` mcermak at redhat dot com [this message]
2015-03-05 17:05 ` [Bug runtime/18083] " jlebon at redhat dot com
2023-12-06 20:33 ` wcohen 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-18083-6586-6npee6biNc@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).