From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug testsuite/5554] sytemtap.syscall failures on ia64.
Date: Fri, 25 Jan 2008 15:33:00 -0000 [thread overview]
Message-ID: <20080125153224.22358.qmail@sourceware.org> (raw)
In-Reply-To: <20080108200751.5554.mhiramat@redhat.com>
------- Additional Comments From wcohen at redhat dot com 2008-01-25 15:32 -------
The checked in patch for bz5554 causes the syscall tests to fail on RHEL4/5
kernel on i386 machines.
Trying to build the systemtap.syscall/sys.stp:
../../install/bin/stap -vv ../../src/testsuite/systemtap.syscall/sys.stp
Ends up producing the following error messages that SEGMENT_RPL_MASK and
USER_RPL undefined on RHEL4 i386 2.6.9-67.0.1.ELsmp and RHEL5 i386
2.6.18-53.1.4.el5:
2dcdef1bb34572403776cda3605b_421823.o
/tmp/stapzirZcY/stap_d39a2dcdef1bb34572403776cda3605b_421823.c
/tmp/stapzirZcY/stap_d39a2dcdef1bb34572403776cda3605b_421823.c: In function
`function___is_user_regs':
/tmp/stapzirZcY/stap_d39a2dcdef1bb34572403776cda3605b_421823.c:33210: error:
`SEGMENT_RPL_MASK' undeclared (first use in this function)
/tmp/stapzirZcY/stap_d39a2dcdef1bb34572403776cda3605b_421823.c:33210: error:
(Each undeclared identifier is reported only once
/tmp/stapzirZcY/stap_d39a2dcdef1bb34572403776cda3605b_421823.c:33210: error: for
each function it appears in.)
/tmp/stapzirZcY/stap_d39a2dcdef1bb34572403776cda3605b_421823.c:33210: error:
`USER_RPL' undeclared (first use in this function)
See that linux-2.6.24/include/asm-x86/segment_32.h has definition for the
SEGMENT_RPL_MASK.
The x86_64 version has:
THIS->__retvalue = (!!((cs & 3)));
For the x86_64 version is it going to return 1 for 1, 2, and 3 in the low bits
of cs. The i386 version is only going to return 1 if the value is 3. Why the
difference in test for x86_64 and i386? The include/asm-x86/ptrace.h has the
same logic. It seems like there could be some simplification there.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
http://sourceware.org/bugzilla/show_bug.cgi?id=5554
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2008-01-25 15:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 20:08 [Bug testsuite/5554] New: " mhiramat at redhat dot com
2008-01-08 21:49 ` [Bug testsuite/5554] " mhiramat at redhat dot com
2008-01-08 21:53 ` mhiramat at redhat dot com
2008-01-09 21:13 ` mhiramat at redhat dot com
2008-01-09 21:14 ` mhiramat at redhat dot com
2008-01-09 21:21 ` mhiramat at redhat dot com
2008-01-09 22:49 ` mhiramat at redhat dot com
2008-01-22 22:49 ` mhiramat at redhat dot com
2008-01-23 0:18 ` fche at redhat dot com
2008-01-23 14:19 ` mhiramat at redhat dot com
2008-01-24 17:03 ` mhiramat at redhat dot com
2008-01-25 15:33 ` wcohen at redhat dot com [this message]
2008-01-25 15:34 ` wcohen at redhat dot com
2008-01-25 15:44 ` mhiramat at redhat dot com
2008-01-28 21:53 ` wcohen at redhat dot com
2008-01-28 22:38 ` mhiramat at redhat dot com
2008-01-29 16:19 ` wcohen at redhat dot com
2008-01-29 16:36 ` fche at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080125153224.22358.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).