[Bug translator/10454] Raw number statement probes won't work without dwarf info

["mjw at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

------- Additional Comments From mjw at redhat dot com  2009-07-31 18:21 -------
Testcase added:

commit 793e611dc277b6943100a5f81274961d526f9b02
Author: Mark Wielaard <mjw@redhat.com>
Date:   Fri Jul 31 19:54:53 2009 +0200

    Add testcase for PR10458, PR10459 and PR10454.
    
    Last test currently disabled because PR10454 is still open.
    
    * testsuite/systemtap.context/uprobe_stmt_num.exp: New file.
    * testsuite/systemtap.context/uprobe_stmt_num.stp: Likewise.
    * testsuite/systemtap.context/uprobe_stmt_num.c: Likewise.

The last test is:

# XXX Last test still fails. PR10454.
return

# Now strip away all debuginfo. Since the script doesn't need any it
# should still work.
set strip_cmd [list "strip" "-g"]
lappend strip_cmd "$testexe"
send_log "Executing: $strip_cmd\n"
eval exec $strip_cmd

stap_run3 $test-run-statements-nodebuginfo -w -g $test-run-statements.stp -c
$testexe

Running this test by hand, removing the -w and adding -vv shows:

stap -vv -g uprobe_stmt_num-run-statements.stp -c
/usr/local/build/systemtap-obj/testsuite/uprobe_stmt_numSystemTap
translator/driver (version 0.9.8/0.141 commit release-0.9.8-218-gf1312b2 + changes)
Copyright (C) 2005-2009 Red Hat, Inc. and others
This is free software; see the source for copying conditions.
Session arch: x86_64 release: 2.6.29.6-213.fc11.x86_64
Created temporary directory "/tmp/stapsGOXP5"
Searched '/usr/local/systemtap/share/systemtap/tapset/x86_64/*.stp', found 3
Searched '/usr/local/systemtap/share/systemtap/tapset/*.stp', found 56
Pass 1: parsed user script and 59 library script(s) in 90usr/0sys/98real ms.
WARNING: cannot find module
/usr/local/build/systemtap-obj/testsuite/uprobe_stmt_num debuginfo: No DWARF
information found
semantic error: no match while resolving probe point
process("uprobe_stmt_num").statement(4195537)
WARNING: cannot find module
/usr/local/build/systemtap-obj/testsuite/uprobe_stmt_num debuginfo: No DWARF
information found
semantic error: no match while resolving probe point
process("uprobe_stmt_num").statement(4195548)
WARNING: cannot find module
/usr/local/build/systemtap-obj/testsuite/uprobe_stmt_num debuginfo: No DWARF
information found
semantic error: no match while resolving probe point
process("uprobe_stmt_num").statement(4195555)
WARNING: cannot find module
/usr/local/build/systemtap-obj/testsuite/uprobe_stmt_num debuginfo: No DWARF
information found
semantic error: no match while resolving probe point
process("uprobe_stmt_num").statement(4195570)
WARNING: cannot find module
/usr/local/build/systemtap-obj/testsuite/uprobe_stmt_num debuginfo: No DWARF
information found
semantic error: no match while resolving probe point
process("uprobe_stmt_num").statement(4195588)
WARNING: cannot find module
/usr/local/build/systemtap-obj/testsuite/uprobe_stmt_num debuginfo: No DWARF
information found
semantic error: no match while resolving probe point
process("uprobe_stmt_num").statement(4195600)
semantic error: no probes found
Pass 2: analyzed script: 0 probe(s), 0 function(s), 0 embed(s), 0 global(s) in
10usr/70sys/85real ms.
Pass 2: analysis failed.  Try again with another '--vp 01' option.
Running rm -rf /tmp/stapsGOXP5

So, when no dwarf info is found the statement probe will just fail even though
no dwarfinfo is needed by the probe body. All probes look like:
probe process("uprobe_stmt_num").statement(0x4004d1)
{
  printf("0x%x\n", uaddr());
}

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=10454

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