public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
* Segmentation fault of probed program during probing.
@ 2011-02-01  6:14 Daniel Fishman
  2011-02-01  6:41 ` Srikar Dronamraju
  2011-02-01  7:54 ` Josh Stone
  0 siblings, 2 replies; 9+ messages in thread
From: Daniel Fishman @ 2011-02-01  6:14 UTC (permalink / raw)
  To: systemtap

Hello,

I am trying to execute the following test script:

probe process("/usr/bin/find").function("*")
{
    printf("%s\n", pp())
}


When I execute the script and run find ('find ./'), find crashes with 
segfault (script itself continues to run).

What is the problem here? Did I ran against some systemtap's safety limit?


Here is output from script's execution:


root@laptop:~/a/systemtap# /opt/systemtap-01feb2010/bin/stap -v test.stp 
Pass 1: parsed user script and 75 library script(s) using 77776virt/21980res/2324shr kb, in 160usr/10sys/169real ms.
Pass 2: analyzed script: 953 probe(s), 1 function(s), 3 embed(s), 0 global(s) using 208944virt/26836res/3628shr kb, in 140usr/720sys/864real ms.
Pass 3: using cached /root/.systemtap/cache/34/stap_34f7f1ae4b5b2093cc71f987d03d63be_188965.c
Pass 4: using cached /root/.systemtap/cache/34/stap_34f7f1ae4b5b2093cc71f987d03d63be_188965.ko
Pass 5: starting run.
process("/usr/bin/find").function("main@/build/buildd/findutils-4.4.2/find/ftsfind.c:657")
process("/usr/bin/find").function("set_option_defaults@/build/buildd/findutils-4.4.2/find/util.c:890")
process("/usr/bin/find").function("check_nofollow@/build/buildd/findutils-4.4.2/find/util.c:252")
process("/usr/bin/find").function("atof@/usr/include/stdlib.h:279")
process("/usr/bin/find").function("now@/build/buildd/findutils-4.4.2/find/util.c:870")
process("/usr/bin/find").function("set_follow_state@/build/buildd/findutils-4.4.2/find/parser.c:438")
process("/usr/bin/find").function("process_leading_options@/build/buildd/findutils-4.4.2/find/util.c:820")
process("/usr/bin/find").function("process_optimisation_option@/build/buildd/findutils-4.4.2/find/util.c:766")
process("/usr/bin/find").function("process_debug_options@/build/buildd/findutils-4.4.2/find/util.c:726")
process("/usr/bin/find").function("build_expression_tree@/build/buildd/findutils-4.4.2/find/tree.c:1190")
process("/usr/bin/find").function("looks_like_expression@/build/buildd/findutils-4.4.2/find/util.c:692")
process("/usr/bin/find").function("find_parser@/build/buildd/findutils-4.4.2/find/parser.c:562")
process("/usr/bin/find").function("found_parser@/build/buildd/findutils-4.4.2/find/parser.c:501")
process("/usr/bin/find").function("find_parser@/build/buildd/findutils-4.4.2/find/parser.c:562")
process("/usr/bin/find").function("found_parser@/build/buildd/findutils-4.4.2/find/parser.c:501")
process("/usr/bin/find").function("find_parser@/build/buildd/findutils-4.4.2/find/parser.c:562")
process("/usr/bin/find").function("found_parser@/build/buildd/findutils-4.4.2/find/parser.c:501")
process("/usr/bin/find").function("parse_openparen@/build/buildd/findutils-4.4.2/find/parser.c:1712")
process("/usr/bin/find").function("get_new_pred_chk_op@/build/buildd/findutils-4.4.2/find/tree.c:1452")
process("/usr/bin/find").function("find_parser@/build/buildd/findutils-4.4.2/find/parser.c:562")
process("/usr/bin/find").function("found_parser@/build/buildd/findutils-4.4.2/find/parser.c:501")
process("/usr/bin/find").function("get_new_pred@/build/buildd/findutils-4.4.2/find/tree.c:1406")
process("/usr/bin/find").function("xmalloc@/build/buildd/findutils-4.4.2/gnulib/lib/xmalloc.c:47")
process("/usr/bin/find").function("init_pred_perf@/build/buildd/findutils-4.4.2/find/tree.c:1390")
process("/usr/bin/find").function("parse_begin_user_args@/build/buildd/findutils-4.4.2/find/parser.c:473")
process("/usr/bin/find").function("pred_sanity_check@/build/buildd/findutils-4.4.2/find/pred.c:2487")
process("/usr/bin/find").function("parse_end_user_args@/build/buildd/findutils-4.4.2/find/parser.c:485")
 

I am using latest systemtap from repository with kernel 2.6.37.

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Segmentation fault of probed program during probing.
  2011-02-01  6:14 Segmentation fault of probed program during probing Daniel Fishman
@ 2011-02-01  6:41 ` Srikar Dronamraju
  2011-02-01  6:49   ` Daniel Fishman
  2011-02-01  7:54 ` Josh Stone
  1 sibling, 1 reply; 9+ messages in thread
From: Srikar Dronamraju @ 2011-02-01  6:41 UTC (permalink / raw)
  To: Daniel Fishman; +Cc: systemtap


Hi Daniel, 

Do you see any hints from output of 'dmesg'?

Also if you have enabled core, then running gdb with core file can
give us more hints.

-- 
Thanks and Regards
Srikar

> Hello,
> 
> I am trying to execute the following test script:
> 
> probe process("/usr/bin/find").function("*")
> {
>     printf("%s\n", pp())
> }
> 
> 
> When I execute the script and run find ('find ./'), find crashes with 
> segfault (script itself continues to run).
> 
> What is the problem here? Did I ran against some systemtap's safety limit?
> 
> 
> Here is output from script's execution:
> 
> 
> root@laptop:~/a/systemtap# /opt/systemtap-01feb2010/bin/stap -v test.stp 
> Pass 1: parsed user script and 75 library script(s) using 77776virt/21980res/2324shr kb, in 160usr/10sys/169real ms.
> Pass 2: analyzed script: 953 probe(s), 1 function(s), 3 embed(s), 0 global(s) using 208944virt/26836res/3628shr kb, in 140usr/720sys/864real ms.
> Pass 3: using cached /root/.systemtap/cache/34/stap_34f7f1ae4b5b2093cc71f987d03d63be_188965.c
> Pass 4: using cached /root/.systemtap/cache/34/stap_34f7f1ae4b5b2093cc71f987d03d63be_188965.ko
> Pass 5: starting run.
> process("/usr/bin/find").function("main@/build/buildd/findutils-4.4.2/find/ftsfind.c:657")
> process("/usr/bin/find").function("set_option_defaults@/build/buildd/findutils-4.4.2/find/util.c:890")
> process("/usr/bin/find").function("check_nofollow@/build/buildd/findutils-4.4.2/find/util.c:252")
> process("/usr/bin/find").function("atof@/usr/include/stdlib.h:279")
> process("/usr/bin/find").function("now@/build/buildd/findutils-4.4.2/find/util.c:870")
> process("/usr/bin/find").function("set_follow_state@/build/buildd/findutils-4.4.2/find/parser.c:438")
> process("/usr/bin/find").function("process_leading_options@/build/buildd/findutils-4.4.2/find/util.c:820")
> process("/usr/bin/find").function("process_optimisation_option@/build/buildd/findutils-4.4.2/find/util.c:766")
> process("/usr/bin/find").function("process_debug_options@/build/buildd/findutils-4.4.2/find/util.c:726")
> process("/usr/bin/find").function("build_expression_tree@/build/buildd/findutils-4.4.2/find/tree.c:1190")
> process("/usr/bin/find").function("looks_like_expression@/build/buildd/findutils-4.4.2/find/util.c:692")
> process("/usr/bin/find").function("find_parser@/build/buildd/findutils-4.4.2/find/parser.c:562")
> process("/usr/bin/find").function("found_parser@/build/buildd/findutils-4.4.2/find/parser.c:501")
> process("/usr/bin/find").function("find_parser@/build/buildd/findutils-4.4.2/find/parser.c:562")
> process("/usr/bin/find").function("found_parser@/build/buildd/findutils-4.4.2/find/parser.c:501")
> process("/usr/bin/find").function("find_parser@/build/buildd/findutils-4.4.2/find/parser.c:562")
> process("/usr/bin/find").function("found_parser@/build/buildd/findutils-4.4.2/find/parser.c:501")
> process("/usr/bin/find").function("parse_openparen@/build/buildd/findutils-4.4.2/find/parser.c:1712")
> process("/usr/bin/find").function("get_new_pred_chk_op@/build/buildd/findutils-4.4.2/find/tree.c:1452")
> process("/usr/bin/find").function("find_parser@/build/buildd/findutils-4.4.2/find/parser.c:562")
> process("/usr/bin/find").function("found_parser@/build/buildd/findutils-4.4.2/find/parser.c:501")
> process("/usr/bin/find").function("get_new_pred@/build/buildd/findutils-4.4.2/find/tree.c:1406")
> process("/usr/bin/find").function("xmalloc@/build/buildd/findutils-4.4.2/gnulib/lib/xmalloc.c:47")
> process("/usr/bin/find").function("init_pred_perf@/build/buildd/findutils-4.4.2/find/tree.c:1390")
> process("/usr/bin/find").function("parse_begin_user_args@/build/buildd/findutils-4.4.2/find/parser.c:473")
> process("/usr/bin/find").function("pred_sanity_check@/build/buildd/findutils-4.4.2/find/pred.c:2487")
> process("/usr/bin/find").function("parse_end_user_args@/build/buildd/findutils-4.4.2/find/parser.c:485")
> 
> 
> I am using latest systemtap from repository with kernel 2.6.37.
> 

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Segmentation fault of probed program during probing.
  2011-02-01  6:41 ` Srikar Dronamraju
@ 2011-02-01  6:49   ` Daniel Fishman
  2011-02-01  6:58     ` Daniel Fishman
  0 siblings, 1 reply; 9+ messages in thread
From: Daniel Fishman @ 2011-02-01  6:49 UTC (permalink / raw)
  To: systemtap

On Tue, 1 Feb 2011 12:04:01 +0530, Srikar Dronamraju <srikar@linux.vnet.ibm.com> wrote:


>Do you see any hints from output of 'dmesg'?

No, there are no messages generated after segfault

>Also if you have enabled core, then running gdb with core file can
>give us more hints.

I enabled core, but unfortunately stack seems corrupted:

(gdb) bt
#0  0xffff8000adc1210e in ?? ()
#1  0x0000000000000000 in ?? ()

Here is registers' state:

rax            0x2	2
rbx            0x7fff52aa1868	140734580267112
rcx            0x799030	7966768
rdx            0x799030	7966768
rsi            0x2	2
rdi            0x7fff52aa1868	140734580267112
rbp            0x42d560	0x42d560
rsp            0x7fff52aa16e0	0x7fff52aa16e0
r8             0x7f2c39354ea8	139827915083432
r9             0x1	1
r10            0x799020	7966752
r11            0x7f2c39052320	139827911926560
r12            0x2	2
r13            0x7fff52aa1860	140734580267104
r14            0x0	0
r15            0x7fff52aa16fc	140734580266748
rip            0xffff8000adc1210e	0xffff8000adc1210e
eflags         0x10246	[ PF ZF IF RF ]
cs             0x33	51
ss             0x2b	43
ds             0x0	0
es             0x0	0
fs             0x0	0
gs             0x0	0
st0            -nan(0x00000000d)	(raw 0xffff000000000000000d)
st1            -nan(0x000000033)	(raw 0xffff0000000000000033)
st2            -nan(0x10000000000000)	(raw 0xffff0010000000000000)
st3            -nan(0x000000002)	(raw 0xffff0000000000000002)
st4            0	(raw 0x00000000000000000000)
st5            0	(raw 0x00000000000000000000)
st6            0	(raw 0x00000000000000000000)
st7            -inf	(raw 0xffff0000000000000000)
fctrl          0x37f	895
fstat          0x0	0
ftag           0xffff	65535
fiseg          0x0	0
fioff          0x0	0
foseg          0x0	0
fooff          0x0	0
fop            0x0	0
xmm0           {v4_float = {0x0, 0x0, 0x0, 0x0}, v2_double = {0x0, 0x0}, v16_int8 = {0x0, 0x0, 0x0, 
    0xff, 0x0 <repeats 12 times>}, v8_int16 = {0x0, 0xff00, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, v4_int32 = {
    0xff000000, 0x0, 0x0, 0x0}, v2_int64 = {0xff000000, 0x0}, 
  uint128 = 0x000000000000000000000000ff000000}
xmm1           {v4_float = {0x0, 0x0, 0x0, 0x0}, v2_double = {0x8000000000000000, 0x8000000000000000}, 
  v16_int8 = {0xff, 0xff, 0xff, 0x0, 0xff <repeats 12 times>}, v8_int16 = {0xffff, 0xff, 0xffff, 
    0xffff, 0xffff, 0xffff, 0xffff, 0xffff}, v4_int32 = {0xffffff, 0xffffffff, 0xffffffff, 
    0xffffffff}, v2_int64 = {0xffffffff00ffffff, 0xffffffffffffffff}, 
  uint128 = 0xffffffffffffffffffffffff00ffffff}
xmm2           {v4_float = {0x0, 0x0, 0x0, 0x0}, v2_double = {0x8000000000000000, 0x0}, v16_int8 = {
    0x61, 0x6e, 0x64, 0x0, 0x65, 0x6e, 0x74, 0x72, 0x79, 0x5f, 0x61, 0x6e, 0x64, 0x20, 0x21, 0x3d}, 
  v8_int16 = {0x6e61, 0x64, 0x6e65, 0x7274, 0x5f79, 0x6e61, 0x2064, 0x3d21}, v4_int32 = {0x646e61, 
    0x72746e65, 0x6e615f79, 0x3d212064}, v2_int64 = {0x72746e6500646e61, 0x3d2120646e615f79}, 
  uint128 = 0x3d2120646e615f7972746e6500646e61}
xmm3           {v4_float = {0x0, 0x0, 0x0, 0x0}, v2_double = {0x0, 0x0}, v16_int8 = {0x0, 0x0, 0x0, 
    0x0, 0xff, 0x0 <repeats 11 times>}, v8_int16 = {0x0, 0x0, 0xff, 0x0, 0x0, 0x0, 0x0, 0x0}, 
  v4_int32 = {0x0, 0xff, 0x0, 0x0}, v2_int64 = {0xff00000000, 0x0}, 
  uint128 = 0x0000000000000000000000ff00000000}
xmm4           {v4_float = {0x0, 0x0, 0x0, 0x0}, v2_double = {0x0, 0x0}, v16_int8 = {
    0x0 <repeats 16 times>}, v8_int16 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, v4_int32 = {0x0, 
    0x0, 0x0, 0x0}, v2_int64 = {0x0, 0x0}, uint128 = 0x00000000000000000000000000000000}
xmm5           {v4_float = {0x0, 0x0, 0x0, 0x0}, v2_double = {0x0, 0x0}, v16_int8 = {
    0x0 <repeats 16 times>}, v8_int16 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, v4_int32 = {0x0, 
    0x0, 0x0, 0x0}, v2_int64 = {0x0, 0x0}, uint128 = 0x00000000000000000000000000000000}
xmm6           {v4_float = {0x0, 0x0, 0x0, 0x0}, v2_double = {0x0, 0x0}, v16_int8 = {
    0x0 <repeats 16 times>}, v8_int16 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, v4_int32 = {0x0, 
    0x0, 0x0, 0x0}, v2_int64 = {0x0, 0x0}, uint128 = 0x00000000000000000000000000000000}
xmm7           {v4_float = {0x0, 0x0, 0x0, 0x0}, v2_double = {0x0, 0x0}, v16_int8 = {
    0x0 <repeats 16 times>}, v8_int16 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, v4_int32 = {0x0, 
    0x0, 0x0, 0x0}, v2_int64 = {0x0, 0x0}, uint128 = 0x00000000000000000000000000000000}
xmm8           {v4_float = {0x0, 0x0, 0x0, 0x0}, v2_double = {0x0, 0x0}, v16_int8 = {
    0x0 <repeats 16 times>}, v8_int16 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, v4_int32 = {0x0, 
    0x0, 0x0, 0x0}, v2_int64 = {0x0, 0x0}, uint128 = 0x00000000000000000000000000000000}
xmm9           {v4_float = {0x0, 0x0, 0x0, 0x0}, v2_double = {0x0, 0x0}, v16_int8 = {
    0x0 <repeats 16 times>}, v8_int16 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, v4_int32 = {0x0, 
    0x0, 0x0, 0x0}, v2_int64 = {0x0, 0x0}, uint128 = 0x00000000000000000000000000000000}
xmm10          {v4_float = {0x0, 0x0, 0x0, 0x0}, v2_double = {0x0, 0x0}, v16_int8 = {
    0x0 <repeats 16 times>}, v8_int16 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, v4_int32 = {0x0, 
    0x0, 0x0, 0x0}, v2_int64 = {0x0, 0x0}, uint128 = 0x00000000000000000000000000000000}
xmm11          {v4_float = {0x0, 0x0, 0x0, 0x0}, v2_double = {0x0, 0x0}, v16_int8 = {
    0x0 <repeats 16 times>}, v8_int16 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, v4_int32 = {0x0, 
    0x0, 0x0, 0x0}, v2_int64 = {0x0, 0x0}, uint128 = 0x00000000000000000000000000000000}
xmm12          {v4_float = {0x0, 0x0, 0x0, 0x0}, v2_double = {0x0, 0x0}, v16_int8 = {
    0x0 <repeats 16 times>}, v8_int16 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, v4_int32 = {0x0, 
    0x0, 0x0, 0x0}, v2_int64 = {0x0, 0x0}, uint128 = 0x00000000000000000000000000000000}
xmm13          {v4_float = {0x0, 0x0, 0x0, 0x0}, v2_double = {0x0, 0x0}, v16_int8 = {
    0x0 <repeats 16 times>}, v8_int16 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, v4_int32 = {0x0, 
    0x0, 0x0, 0x0}, v2_int64 = {0x0, 0x0}, uint128 = 0x00000000000000000000000000000000}
xmm14          {v4_float = {0x0, 0x0, 0x0, 0x0}, v2_double = {0x0, 0x0}, v16_int8 = {
    0x0 <repeats 16 times>}, v8_int16 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, v4_int32 = {0x0, 
    0x0, 0x0, 0x0}, v2_int64 = {0x0, 0x0}, uint128 = 0x00000000000000000000000000000000}
xmm15          {v4_float = {0x0, 0x0, 0x0, 0x0}, v2_double = {0x0, 0x0}, v16_int8 = {
    0x0 <repeats 16 times>}, v8_int16 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, v4_int32 = {0x0, 
    0x0, 0x0, 0x0}, v2_int64 = {0x0, 0x0}, uint128 = 0x00000000000000000000000000000000}
mxcsr          0x1fa0	[ PE IM DM ZM OM UM PM ]


Is there is anything else I can provide?

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Segmentation fault of probed program during probing.
  2011-02-01  6:49   ` Daniel Fishman
@ 2011-02-01  6:58     ` Daniel Fishman
  0 siblings, 0 replies; 9+ messages in thread
From: Daniel Fishman @ 2011-02-01  6:58 UTC (permalink / raw)
  To: systemtap

On Tue, 01 Feb 2011 08:48:24 +0200, Daniel Fishman <quantera@gmail.com> wrote:

I simplified the script using empty probe body - segfault still occurs.

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Segmentation fault of probed program during probing.
  2011-02-01  6:14 Segmentation fault of probed program during probing Daniel Fishman
  2011-02-01  6:41 ` Srikar Dronamraju
@ 2011-02-01  7:54 ` Josh Stone
  2011-02-01  8:09   ` Daniel Fishman
  1 sibling, 1 reply; 9+ messages in thread
From: Josh Stone @ 2011-02-01  7:54 UTC (permalink / raw)
  To: quantera; +Cc: systemtap

On 01/31/2011 10:14 PM, Daniel Fishman wrote:
> When I execute the script and run find ('find ./'), find crashes with 
> segfault (script itself continues to run).
> 
> What is the problem here? Did I ran against some systemtap's safety limit?
[...]
> I am using latest systemtap from repository with kernel 2.6.37.

What version of elfutils are you running with?  We recently found some
issue with address calculations on prelinked binaries, which should
hopefully be fixed in elfutils 0.151.

Josh

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Segmentation fault of probed program during probing.
  2011-02-01  7:54 ` Josh Stone
@ 2011-02-01  8:09   ` Daniel Fishman
  2011-02-01  8:33     ` Josh Stone
  0 siblings, 1 reply; 9+ messages in thread
From: Daniel Fishman @ 2011-02-01  8:09 UTC (permalink / raw)
  To: systemtap

On Mon, 31 Jan 2011 23:53:56 -0800, Josh Stone <jistone@redhat.com> wrote:

>What version of elfutils are you running with?  We recently found some
>issue with address calculations on prelinked binaries, which should
>hopefully be fixed in elfutils 0.151.

System uses elfutils 0.147. Systemtap was built with elfutils 0.151.

Is it necessary to change system's elfutils in order to prevent the crash
or is building systemtap with new version excludes possibility of the
problem you are talking about (and therefore there is other reason for
the crash)?

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Segmentation fault of probed program during probing.
  2011-02-01  8:09   ` Daniel Fishman
@ 2011-02-01  8:33     ` Josh Stone
  2011-02-01 17:21       ` Daniel Fishman
  0 siblings, 1 reply; 9+ messages in thread
From: Josh Stone @ 2011-02-01  8:33 UTC (permalink / raw)
  To: quantera; +Cc: systemtap

On 02/01/2011 12:08 AM, Daniel Fishman wrote:
> On Mon, 31 Jan 2011 23:53:56 -0800, Josh Stone <jistone@redhat.com> wrote:
> 
>> What version of elfutils are you running with?  We recently found some
>> issue with address calculations on prelinked binaries, which should
>> hopefully be fixed in elfutils 0.151.
> 
> System uses elfutils 0.147. Systemtap was built with elfutils 0.151.
> 
> Is it necessary to change system's elfutils in order to prevent the crash
> or is building systemtap with new version excludes possibility of the
> problem you are talking about (and therefore there is other reason for
> the crash)?

You built using --with-elfutils pointing to 0.151?  That should suffice,
but "stap -V" will tell for sure.

I'm able to reproduce it just now on Fedora 14 x86_64, stap.git and
elfutils-0.151.  Then I tried "prelink -u /usr/bin/find", and the
crashes went away, so it seems Roland and I will need to do more
analysis on the elfutils/prelink problem...

Josh

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Segmentation fault of probed program during probing.
  2011-02-01  8:33     ` Josh Stone
@ 2011-02-01 17:21       ` Daniel Fishman
  2011-02-01 23:38         ` Josh Stone
  0 siblings, 1 reply; 9+ messages in thread
From: Daniel Fishman @ 2011-02-01 17:21 UTC (permalink / raw)
  To: systemtap

On Tue, 01 Feb 2011 00:33:11 -0800, in gmane.linux.systemtap Josh Stone <jistone@redhat.com> wrote:

>You built using --with-elfutils pointing to 0.151?  That should suffice,
>but "stap -V" will tell for sure.

Yes:

root@laptop:~/a/systemtap# /opt/systemtap-01feb2010/bin/stap -V
SystemTap translator/driver (version 1.5/0.151 commit release-1.4-36-g4b12854)
Copyright (C) 2005-2011 Red Hat, Inc. and others
This is free software; see the source for copying conditions.
enabled features: AVAHI LIBSQLITE3 NSS BOOST_SHARED_PTR TR1_UNORDERED_MAP

>I'm able to reproduce it just now on Fedora 14 x86_64, stap.git and
>elfutils-0.151.  Then I tried "prelink -u /usr/bin/find", and the
>crashes went away, so it seems Roland and I will need to do more
>analysis on the elfutils/prelink problem...

P.S.: in situations like this (when problem is recognized as a bug and
is reproducable) should I still open a bug, or is recognition of a problem
by devs is enough?


^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Segmentation fault of probed program during probing.
  2011-02-01 17:21       ` Daniel Fishman
@ 2011-02-01 23:38         ` Josh Stone
  0 siblings, 0 replies; 9+ messages in thread
From: Josh Stone @ 2011-02-01 23:38 UTC (permalink / raw)
  To: quantera; +Cc: systemtap

On 02/01/2011 09:20 AM, Daniel Fishman wrote:
> P.S.: in situations like this (when problem is recognized as a bug and
> is reproducable) should I still open a bug, or is recognition of a problem
> by devs is enough?

Sure, once an issue confirmed not to be user error, we want to have a
bug tracking it, and we wouldn't mind if you were to open it.  I went
ahead and filed this one though - please feel free to CC yourself.
  http://sourceware.org/bugzilla/show_bug.cgi?id=12458

Thanks,
Josh

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2011-02-01 23:38 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-02-01  6:14 Segmentation fault of probed program during probing Daniel Fishman
2011-02-01  6:41 ` Srikar Dronamraju
2011-02-01  6:49   ` Daniel Fishman
2011-02-01  6:58     ` Daniel Fishman
2011-02-01  7:54 ` Josh Stone
2011-02-01  8:09   ` Daniel Fishman
2011-02-01  8:33     ` Josh Stone
2011-02-01 17:21       ` Daniel Fishman
2011-02-01 23:38         ` Josh Stone

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).