[Bug dyninst/21223] New: Function return probe is not executed in dyninst mode

[jackdev at mailbox dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=21223

            Bug ID: 21223
           Summary: Function return probe is not executed in dyninst mode
           Product: systemtap
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: dyninst
          Assignee: systemtap at sourceware dot org
          Reporter: jackdev at mailbox dot org
  Target Milestone: ---

Created attachment 9873
  --> https://sourceware.org/bugzilla/attachment.cgi?id=9873&action=edit
extensive stap log

Hi,

I am currently having a weird issue with systemtap and dyninst.
I'm using systemtap 3.1 and dyninst 9.3.0 (both built from sources) along with
gcc 4.9.4

The return probe process.function("factor").return is not getting in my
application. However, it is correctly executed in a minimal working example.
I have not been able to figure out where the difference comes from.

My stap script (runtime_dyninst.stp): https://paste.debian.net/hidden/859190a9/
> #!/usr/bin/stap
> 
> probe process.function("factor") {
>    printf("Entered function factor\n")
> }
> 
> probe process.function("factor").return {
>     printf("Left function factor")
> }

Minimal Working Example (min.c): https://paste.debian.net/hidden/beaf61d0/

My program (simple.c): https://paste.debian.net/hidden/07281df0/

Both programs were compiled with: 'gcc -g -O0 -lm'

Minimal working example (min.c):
> $ stap --dyninst -c './min 123' runtime_dyninst.stp
> Entered function factor
> Left function factor
> $

My application (simple.c):
> $ stap --dyninst -c './simple 123' runtime_dyninst.stp
> Entered function factor
> $

More extensive logs are attached. I'm happy to provide more information if
needed.

Greetings
Jack

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