[Bug runtime/5085] New: print_backtrace() and backtrace() not working in timer.profile probe on 2.6.23-rc8 kernel

[Bug runtime/5085] New: print_backtrace() and backtrace() not working in timer.profile probe on 2.6.23-rc8 kernel

[wcohen at redhat dot com]

With the 2.6.23-rc8 kernel the following tests fail:

FAIL: backtrace of timer.profile (1)
FAIL: print_stack of timer.profile (0)

This is from testsuite/systemtap.context/backtrace.stp. Looking through the
systemtap.log see bogus addresses like the following:

--------

backtrace from timer.profile:

 0x001d3392

--------

the profile stack is 0x001d3392

--------

 0x001d3392

--------

Note that the test is passing on the same machine with the standard RHEL4
kernel,  2.6.9-55.0.9.ELsmp

-- 
           Summary: print_backtrace() and  backtrace() not working in
                    timer.profile probe on 2.6.23-rc8 kernel
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: wcohen at redhat dot com
  GCC host triplet: i686


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

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

[Bug runtime/5085] print_backtrace() and backtrace() not working in timer.profile probe on 2.6.23-rc8 kernel

[mhiramat at redhat dot com]

------- Additional Comments From mhiramat at redhat dot com  2007-10-02 15:19 -------
(In reply to comment #0)
> backtrace from timer.profile:
> 
>  0x001d3392
> 
> --------
> 
> the profile stack is 0x001d3392
> 
> --------
> 
>  0x001d3392
> 

It was reproduced on my machine with 2.6.22.9-91.fc7.
timer.profile will be invoked when a user program is running, and backtracing
fails on user stack.
I think we need to introduce a function to check whether the probe is in the
kernel or in user mode.


-- 


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

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

[Bug runtime/5085] print_backtrace() and backtrace() not working in timer.profile probe on 2.6.23-rc8 kernel

[joshua dot i dot stone at intel dot com]

------- Additional Comments From joshua dot i dot stone at intel dot com  2007-10-02 15:20 -------
Why do you say that is bogus?  Those look like a userspace address, which is
reasonable for timer.profile...

-- 


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

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

[Bug testsuite/5085] print_backtrace() and backtrace() not working in timer.profile probe on 2.6.23-rc8 kernel

[wcohen at redhat dot com]

------- Additional Comments From wcohen at redhat dot com  2007-10-02 15:40 -------
"bogus" is a poor choice of words. the test should be more forgiving of
userspace values.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|runtime                     |testsuite


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

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

[Bug testsuite/5085] print_backtrace() and backtrace() not working in timer.profile probe on 2.6.23-rc8 kernel

[mhiramat at redhat dot com]

------- Additional Comments From mhiramat at redhat dot com  2007-10-02 15:57 -------
In user space, probefunc() returns "". So, the test can skip if the profile
probe is in user mode.


-- 


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

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

[Bug testsuite/5085] print_backtrace() and backtrace() not working in timer.profile probe on 2.6.23-rc8 kernel

[hunt at redhat dot com]

------- Additional Comments From hunt at redhat dot com  2007-10-02 18:20 -------
(In reply to comment #3)
> "bogus" is a poor choice of words. the test should be more forgiving of
> userspace values.

I thought I fixed this last week.  Do you have this in testsuite/ChangeLog?
2007-09-25  Martin Hunt  <hunt@redhat.com>

        * systemtap.context/backtrace.tcl: Handle single line timer.profile
        backtraces.

-- 


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

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

[Bug testsuite/5085] print_backtrace() and backtrace() not working in timer.profile probe on 2.6.23-rc8 kernel

[mhiramat at redhat dot com]

------- Additional Comments From mhiramat at redhat dot com  2007-10-03 19:54 -------
(In reply to comment #5)
> I thought I fixed this last week.  Do you have this in testsuite/ChangeLog?
> 2007-09-25  Martin Hunt  <hunt@redhat.com>
> 
>         * systemtap.context/backtrace.tcl: Handle single line timer.profile
>         backtraces.

Thanks to fix that, however, I think that is not related to this issue.
(In my case, I used the latest cvs source code.)

it is hard to get the function name from userspace without debuginfo of the
application. So, I recommend to skip the timer.profile handler in the test if it
is invoked in userspace. I think we can check that by using probefunc().


-- 


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

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

[Bug testsuite/5085] print_backtrace() and backtrace() not working in timer.profile probe on 2.6.23-rc8 kernel

[mhiramat at redhat dot com]

------- Additional Comments From mhiramat at redhat dot com  2007-10-23 18:28 -------
(In reply to comment #6)
> it is hard to get the function name from userspace without debuginfo of the
> application. So, I recommend to skip the timer.profile handler in the test if it
> is invoked in userspace. I think we can check that by using probefunc().

I think we can check it by introducing new user_mode() function which just
invokes user_mode() macro.


-- 


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

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

[Bug testsuite/5085] print_backtrace() and backtrace() not working in timer.profile probe on 2.6.23-rc8 kernel

[fche at redhat dot com]

------- Additional Comments From fche at redhat dot com  2008-11-06 03:27 -------
User-space backtracing should work.


*** This bug has been marked as a duplicate of 5635 ***

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |DUPLICATE


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

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