public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Stefan Liebler <stli@linux.vnet.ibm.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH] S390: Sync ptrace.h with kernel. [BZ #21539]
Date: Fri, 30 Jun 2017 10:09:00 -0000	[thread overview]
Message-ID: <a0750c84-154a-e24c-acfd-4899ce67a1ef@redhat.com> (raw)
In-Reply-To: <a70194fb-d96c-d22f-7aba-36be9685d421@linux.vnet.ibm.com>

On 06/19/2017 03:10 PM, Stefan Liebler wrote:
>     	* sysdeps/unix/sysv/linux/s390/tst-ptrace-singleblock.c:
>     	New file.

The test fails for me like this on s390x:

[root@ibm-z-25 build]# bash testrun.sh misc/tst-ptrace-singleblock
cat /proc/23548/maps
80000000-80004000 r-xp 00000000 fd:00 1883202
/root/build/misc/tst-ptrace-singleblock
80004000-80005000 r--p 00003000 fd:00 1883202
/root/build/misc/tst-ptrace-singleblock
80005000-80006000 rw-p 00004000 fd:00 1883202
/root/build/misc/tst-ptrace-singleblock
2aa00794000-2aa007ba000 r-xp 00000000 fd:00 34794498
/root/build/elf/ld.so
2aa007ba000-2aa007bb000 r--p 00025000 fd:00 34794498
/root/build/elf/ld.so
2aa007bb000-2aa007bd000 rw-p 00026000 fd:00 34794498
/root/build/elf/ld.so
3fffd1e9000-3fffd1ea000 rw-s 00000000 00:04 146001
/dev/zero (deleted)
3fffd1ea000-3fffd1ec000 rw-p 00000000 00:00 0
3fffd1ec000-3fffd38d000 r-xp 00000000 fd:00 34794501
/root/build/libc.so
3fffd38d000-3fffd391000 r--p 001a0000 fd:00 34794501
/root/build/libc.so
3fffd391000-3fffd393000 rw-p 001a4000 fd:00 34794501
/root/build/libc.so
3fffd393000-3fffd39a000 rw-p 00000000 00:00 0
3ffffe62000-3fffff83000 rw-p 00000000 00:00 0
[stack]
child IA: 0x3fffd22ac62 last_break: 0x2aa0079e218
error: ../sysdeps/unix/sysv/linux/s390/tst-ptrace-singleblock.c:111: not
true: ptrace (req_singleblock, pid, NULL, NULL) == 0
The PTRACE_SINGLEBLOCK of the tracer will stop after: brasl %r14,<puts@plt>!
error: 1 test failures
[root@ibm-z-25 build]#

Relevant package versions:

kernel-3.10.0-689.el7.s390x
kernel-headers-3.10.0-689.el7.s390x
devtoolset-6-gcc-6.3.1-3.1.el7.s390x

Please let me know if you need additional information to debug this.

Thanks,
Florian

  parent reply	other threads:[~2017-06-30 10:09 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-06 10:17 Stefan Liebler
2017-06-06 10:44 ` Andreas Schwab
2017-06-06 10:58   ` Dmitry V. Levin
2017-06-06 11:56   ` Stefan Liebler
2017-06-08 12:02     ` Stefan Liebler
2017-06-13 20:05 ` Dmitry V. Levin
2017-06-19 13:11   ` Stefan Liebler
2017-06-19 13:26     ` Dmitry V. Levin
2017-06-19 14:34       ` Stefan Liebler
2017-06-30 10:09     ` Florian Weimer [this message]
2017-07-04  8:22       ` Stefan Liebler
2017-07-04  9:41         ` Florian Weimer
2017-07-04 15:37           ` Stefan Liebler
2017-07-07 10:22             ` Stefan Liebler
2017-07-07 10:45               ` Florian Weimer
2017-07-07 13:54                 ` Stefan Liebler
2017-07-11  8:39                   ` Stefan Liebler
2017-07-18 10:20     ` Dmitry V. Levin
2017-07-18 13:31       ` Carlos O'Donell
2017-07-18 13:39         ` Dmitry V. Levin
2017-07-18 14:11           ` Carlos O'Donell
2017-07-18 14:28             ` Mark Wielaard
2017-07-18 14:40               ` Mark Wielaard
2017-07-20  7:38             ` Stefan Liebler
2017-07-20  8:07               ` Carlos O'Donell
2017-07-20  8:32                 ` Stefan Liebler
2017-07-24  3:51                   ` Dmitry V. Levin
2017-07-24  7:18                     ` Stefan Liebler
2017-07-18 13:41       ` Stefan Liebler
2017-07-18 14:12         ` Carlos O'Donell
2017-07-18 14:16         ` Dmitry V. Levin
2017-07-19  8:40           ` Stefan Liebler

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=a0750c84-154a-e24c-acfd-4899ce67a1ef@redhat.com \
    --to=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=stli@linux.vnet.ibm.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).