This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug dyninst/17360] systemtap in the dyninst mode kills the probed binary
- From: "mcermak at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Mon, 08 Sep 2014 13:09:03 +0000
- Subject: [Bug dyninst/17360] systemtap in the dyninst mode kills the probed binary
- Auto-submitted: auto-generated
- References: <bug-17360-6586 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17360
--- Comment #1 from Martin Cermak <mcermak at redhat dot com> ---
Similar case:
=====
# cat test.c
int main() {while(1); return(0);}
# gcc -g test.c
# ./a.out &
[13] 5664
# pid=$!; stap --runtime=dyninst -x $pid -e 'probe
process.function("*"){log(pp()); exit()}'
stapdyn: WARNING: Couldn't convert /root/work/1/a.out+0 to an address
stapdyn: WARNING: Couldn't instrument the function containing 0x400430,
/root/work/1/a.out+0x430
stapdyn: WARNING: Couldn't instrument the function containing 0x400460,
/root/work/1/a.out+0x460
process("/root/work/1/a.out").function("main@/root/work/1/test.c:1")
[13]+ Segmentation fault ./a.out
#
=====
I believe also in the aforementioned case the app segfaulted. By tha way, are
these warnings expected?
--
You are receiving this mail because:
You are the assignee for the bug.