[Bug tapsets/5555] New: signal-all-probes.stp and proc_snoop.stp fail on ia64

[Bug tapsets/5555] New: signal-all-probes.stp and proc_snoop.stp fail on ia64

[mhiramat at redhat dot com]

Both of signal-all-probes.stp and proc_snoop.stp cause semantic errors
due to failure of retrieving local variables on ia64.

I found handle_signal() which is the probed function 
was automatically inlined.

$ grep handle_signal /proc/kallsyms || echo "not found"
not found
$

=============
starting /home/mhiramat/work/src/testsuite/buildok/signal-all-probes.stp
spawn1 stap -p4 /home/mhiramat/work/src/testsuite/buildok/signal-all-probes.stp
semantic error: failed to retrieve location attribute for local 'info' (dieoffse
t: 0xdf1ed): identifier '$info' at /usr/local/share/systemtap/tapset/signal.stp:
392:13
semantic error: failed to retrieve location attribute for local 'info' (dieoffse
t: 0xdf1ed): identifier '$info' at /usr/local/share/systemtap/tapset/signal.stp:
392:13
semantic error: failed to retrieve location attribute for local 'info' (dieoffse
t: 0xdf1ed): identifier '$info' at /usr/local/share/systemtap/tapset/signal.stp:
393:16

semantic error: failed to retrieve location attribute for local 'info' (dieoffse
t: 0xdf1ed): identifier '$info' at /usr/local/share/systemtap/tapset/signal.stp:
393:16
Pass 2: analysis failed.  Try again with more '-v' (verbose) options.

Pass 2: analysis failed.  Try again with more '-v' (verbose) options.
wait results: 4014 exp17 0 1
FAIL: buildok/signal-all-probes.stp
=============
FAIL: proc_snoop.stp
semantic error: failed to retrieve location attribute for local 'sig' (dieoffset
: 0xdf1f7): identifier '$sig' at /usr/local/share/systemtap/tapset/signal.stp:39
0:11
semantic error: failed to retrieve location attribute for local 'sig' (dieoffset
: 0xdf1f7): identifier '$sig' at /usr/local/share/systemtap/tapset/signal.stp:39
1:29
semantic error: failed to retrieve location attribute for local 'info' (dieoffse
t: 0xdf1ed): identifier '$info' at /usr/local/share/systemtap/tapset/signal.stp:
392:13
semantic error: failed to retrieve location attribute for local 'info' (dieoffse
t: 0xdf1ed): identifier '$info' at /usr/local/share/systemtap/tapset/signal.stp:
393:16
Pass 2: analysis failed.  Try again with more '-v' (verbose) options.
=============

-- 
           Summary: signal-all-probes.stp and proc_snoop.stp fail on ia64
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tapsets
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: mhiramat at redhat dot com


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

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

[Bug tapsets/5555] signal-all-probes.stp and proc_snoop.stp fail on ia64

[mhiramat at redhat dot com]

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
 GCC target triplet|                            |ia64


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

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

[Bug tapsets/5555] signal-all-probes.stp and proc_snoop.stp fail on ia64

[mhiramat at redhat dot com]

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
   GCC host triplet|                            |ia64
 GCC target triplet|ia64                        |


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

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

[Bug tapsets/5555] signal-all-probes.stp and proc_snoop.stp fail on ia64

[srinivasa at in dot ibm dot com]

------- Additional Comments From srinivasa at in dot ibm dot com  2008-01-09 11:16 -------
Even I face the same problem in ppc64(But I was not aware of ia64 case). I have 
proposed the patch in bug#5151.
=========================================
 tapset/signal.stp |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

Index: src/tapset/signal.stp
===================================================================
--- src.orig/tapset/signal.stp
+++ src/tapset/signal.stp
@@ -385,7 +385,8 @@ probe signal.pending.return = kernel.fun
  *  regs   : Address in the Kernel Mode stack area 
  *  
  */
-probe signal.handle = kernel.function("handle_signal")
+probe signal.handle = kernel.function("handle_signal") ?  ,
+                       kernel.function("handle_signal32") ?
 {
     sig = $sig
     sig_name = _signal_name($sig)
=================================================

Please find the equivalent function of handle_signal() in IA64 and add it here.

Thanks
 Srinivasa DS




-- 


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

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

[Bug tapsets/5555] signal-all-probes.stp and proc_snoop.stp fail on ia64

[fche at redhat dot com]

------- Additional Comments From fche at redhat dot com  2008-01-09 14:42 -------
> -probe signal.handle = kernel.function("handle_signal")
> +probe signal.handle = kernel.function("handle_signal") ?  ,
> +                       kernel.function("handle_signal32") ?

Why would both handle_signal and handle_signal32 be marked optional?
Could one of them be favoured with the "!" (optional & sufficient)
designation?


-- 


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

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

[Bug tapsets/5555] signal-all-probes.stp and proc_snoop.stp fail on ia64

[mhiramat at redhat dot com]

------- Additional Comments From mhiramat at redhat dot com  2008-01-09 16:25 -------
As far as I can see, there is no equivalents of handle_signal on ia64.
One possible solution (just for passing tests!) is adding "?, never" to the
signal.handle probepoint.

However, I think it depends on bz1155(inline function parameters).


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
  BugsThisDependsOn|                            |1155


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

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

[Bug tapsets/5555] signal-all-probes.stp and proc_snoop.stp fail on ia64

[fche at redhat dot com]

-- 
Bug 5555 depends on bug 1155, which changed state.

Bug 1155 Summary: inline function parameters
http://sourceware.org/bugzilla/show_bug.cgi?id=1155

           What    |Old Value                   |New Value
----------------------------------------------------------------------------
             Status|SUSPENDED                   |RESOLVED
         Resolution|                            |FIXED

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

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

[Bug tapsets/5555] signal-all-probes.stp and proc_snoop.stp fail on ia64

[fche at redhat dot com]

------- Additional Comments From fche at redhat dot com  2010-05-21 19:40 -------
With recent gcc, inline function arguments are more consistently accessible as
$vars.

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


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

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