This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug translator/10602] REG_IP() used as lvalue fails on s390x, probably ia64


------- Additional Comments From jkenisto at us dot ibm dot com  2009-09-04 18:15 -------
(In reply to comment #5)
> Jim, I applied the patch (10602.patch1) that you provide on systemtap-0.9.9 and
> it addressed the lvalue issue I was seeing on a SLES11 S390x system. I also
> updated my git tree to the current head (commit a5d268f) and ran this version
> also. The current tree addressed my lvalue issue also.
> 
> While both versions addressed the lvalue issue now I am now seeing a frame size
> error.
> 
> "/root/andmike/systemtap-a5d268f/share/systemtap/runtime/transport/control.c: In
> function ?_stp_ctl_write_cmd?:
> /root/andmike/systemtap-a5d268f/share/systemtap/runtime/transport/control.c:77:
> error: frame size of ?_stp_ctl_write_cmd? is 288 bytes"
> 
> 

Let's track this as a different bug.  Mike, will you open a PR for this?  It'd
be good to include the output from stap --vp 0003 (which will show the gcc
options in use) and cc -v (to get the gcc version number, etc.).

I don't know why a 288-byte frame is considered an error.  Too big for a kernel
function?  I don't see anything in _stp_ctl_write_cmd() that would yield a big
stack frame.

-- 


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

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]