[Bug translator/4899] New: Can't insert stap probes on empty lines in a C function

[Bug translator/4899] New: Can't insert stap probes on empty lines in a C function

[bharata at linux dot vnet dot ibm dot com]

Using SystemTap translator/driver (version 0.5.15/Red Hat elfutils 0.125 built
2007-08-01)

If a probepoint falls on an empty line in a C function, stap throw's a semantic
error. For eg with this stap script,

# kernel/fork.c:1385 happens to be a line w/o any C statements in do_fork() in
the kernel I am using.
probe kernel.function("*@kernel/fork.c:1385") {
        printf("do_fork: %d\n", $clone_flags);
}

The error shown is:
semantic error: no match for probe point while resolving probe point
kernel.function("*@kernel/fork.c:1385")

I would think that stap needs to find the next valid line which has a C
statement and should insert the probepoint there.

-- 
           Summary: Can't insert stap probes on empty lines in a C function
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: translator
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: bharata at linux dot vnet dot ibm dot com


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

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

[Bug translator/4899] Can't insert stap probes on empty lines in a C function

[fche at redhat dot com]

------- Additional Comments From fche at redhat dot com  2007-08-20 21:36 -------
This problem hits people easily if they need to use .statement() probes.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|systemtap at sources dot    |fche at redhat dot com
                   |redhat dot com              |
             Status|NEW                         |ASSIGNED


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

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