Preparing for the next release: call for testing

[Mike Frysinger]

On 02 Mar 2015 14:31, Dmitry V. Levin wrote:
> On Mon, Mar 02, 2015 at 12:42:45AM -0500, Mike Frysinger wrote:
> >  - x32 statfs tracing of x86 binaries fails ?
> 
> I'd like to see the log.  There are two test-suite.log files on x32,
> but only tests/test-suite.log is printed.

FAIL: statfs
============

execve("./statfs", ["./statfs"], [/* 44 vars */]) = 0
[ Process PID=476 runs in 32 bit mode. ]
access("/etc/ld.so.preload", R_OK)      = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
open("/lib/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
statfs64("/proc/self/status", 84, {???}) = 0
+++ exited with 0 +++
statfs.test: failed test: ../strace -efile ./statfs failed to trace "statfs(64)?" properly
FAIL statfs.test (exit status: 1)

> On s390, besides kernel bug with si_addr, all printed instruction pointers
> have 0x80000000 bit set.  If it isn't a kernel bug (and it doesn't look like
> one), then it's a strace bug in not taking some s390 address mapping
> feature into account.

since it's not a regression and no one has complained yet, and we know s390 is 
broken in at least one way, i think we just wait for the kernel guys to respond 
before we spend more time investigating.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.strace.io/pipermail/strace-devel/attachments/20150302/d343d823/attachment.bin>