From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7494 invoked by alias); 4 Sep 2009 18:15:45 -0000 Received: (qmail 7454 invoked by uid 48); 4 Sep 2009 18:15:33 -0000 Date: Fri, 04 Sep 2009 18:15:00 -0000 Message-ID: <20090904181533.7453.qmail@sourceware.org> From: "jkenisto at us dot ibm dot com" To: systemtap@sources.redhat.com In-Reply-To: <20090903224929.10602.jkenisto@us.ibm.com> References: <20090903224929.10602.jkenisto@us.ibm.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug translator/10602] REG_IP() used as lvalue fails on s390x, probably ia64 X-Bugzilla-Reason: AssignedTo Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2009-q3/txt/msg00577.txt.bz2 ------- 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.