[Bug gdb/16468] New: gdb fails on s390x with "Couldn't write registers: Invalid argument"

[Bug gdb/16468] New: gdb fails on s390x with "Couldn't write registers: Invalid argument"

[naesten at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16468

            Bug ID: 16468
           Summary: gdb fails on s390x with "Couldn't write registers:
                    Invalid argument"
           Product: gdb
           Version: 7.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: naesten at gmail dot com

Some of us at Debian have noticed that GDB isn't working in s390x sid chroots
on the s390 porterbox, zelenka.debian.org.

Observe:

sbronson@zelenka:~/strace-code$ uname -a
Linux zelenka 3.2.0-4-s390x #1 SMP Debian 3.2.51-1 s390x GNU/Linux
sbronson@zelenka:~/strace-code$ dpkg-query -W linux-image-3.2.0-4-s390x
linux-image-3.2.0-4-s390x       3.2.51-1
sbronson@zelenka:~/strace-code$ schroot -r -c $CHROOT
<-code$ strace -e ptrace gdb -batch -ex run -ex bt --args echo foo
--- SIGCHLD (Child exited) @ 0 (0) ---
--- SIGCHLD (Child exited) @ 0 (0) ---
ptrace(PTRACE_CONT, 22210, 0x1, SIG_0)  = 0
--- SIGCHLD (Child exited) @ 0 (0) ---
ptrace(PTRACE_SETOPTIONS, 22210, 0, PTRACE_O_TRACEFORK) = 0
ptrace(PTRACE_SETOPTIONS, 22211, 0, PTRACE_O_TRACEFORK) = 0
ptrace(PTRACE_SETOPTIONS, 22211, 0, PTRACE_O_TRACEFORK|PTRACE_O_TRACEVFORKDONE)
= 0
ptrace(PTRACE_CONT, 22211, 0, SIG_0)    = 0
ptrace(PTRACE_GETEVENTMSG, 22211, 0, 0x3ffffdb1af8) = 0
ptrace(PTRACE_KILL, 22212, 0, 0)        = 0
ptrace(PTRACE_KILL, 22211, 0, 0)        = 0
--- SIGCHLD (Child exited) @ 0 (0) ---
ptrace(PTRACE_SETOPTIONS, 22210, 0,
PTRACE_O_TRACEFORK|PTRACE_O_TRACEVFORK|PTRACE_O_TRACECLONE|PTRACE_O_TRACEEXEC|PTRACE_O_TRACEVFORKDONE)
= 0
ptrace(PTRACE_SETOPTIONS, 22210, 0, PTRACE_O_TRACESYSGOOD) = 0
ptrace(PTRACE_SETOPTIONS, 22210, 0,
PTRACE_O_TRACESYSGOOD|PTRACE_O_TRACEFORK|PTRACE_O_TRACEVFORK|PTRACE_O_TRACECLONE|PTRACE_O_TRACEEXEC|PTRACE_O_TRACEVFORKDONE)
= 0
ptrace(0x4204 /* PTRACE_??? */, 22210, 0x306, 0x3ffffdb1cb8) = 0
ptrace(0x4204 /* PTRACE_??? */, 22210, 0x307, 0x3ffffdb1cb8) = 0
ptrace(PTRACE_PEEKUSER, 22210, psw_mask, [0x705c00180000000]) = 0
ptrace(0x5000 /* PTRACE_??? */, 22210, 0x3ffffdb1af0, 0x3fffcc2db28) = 0
ptrace(PTRACE_PEEKUSER, 22210, psw_mask, [0x705c00180000000]) = 0
.
.
.
ptrace(PTRACE_PEEKUSER, 22210, psw_mask, [0x705c00180000000]) = 0
ptrace(PTRACE_PEEKTEXT, 22210, 0x80007ef8, [0]) = 0
ptrace(PTRACE_PEEKUSER, 22210, psw_mask, [0x705c00180000000]) = 0
.
.
.
ptrace(PTRACE_PEEKUSER, 22210, psw_mask, [0x705c00180000000]) = 0
ptrace(PTRACE_PEEKTEXT, 22210, 0x80007ef8, [0]) = 0
ptrace(0x4204 /* PTRACE_??? */, 22210, 0x307, 0x3ffffdb19e8) = 0
ptrace(0x4205 /* PTRACE_??? */, 22210, 0x307, 0x3ffffdb19e8) = 0
ptrace(PTRACE_PEEKTEXT, 22210, 0x3fffdfeb6d0, [0xfddc070707fe0707]) = 0
ptrace(PTRACE_PEEKTEXT, 22210, 0x3fffdfeb6d0, [0xfddc070707fe0707]) = 0
ptrace(PTRACE_POKEDATA, 22210, 0x3fffdfeb6d0, 0xfddc070700010707) = 0
ptrace(PTRACE_CONT, 22210, 0x1, SIG_0)  = 0
--- SIGCHLD (Child exited) @ 0 (0) ---
ptrace(0x5000 /* PTRACE_??? */, 22210, 0x3ffffdb1548, 0x3fffcc2db28) = 0
ptrace(0x5000 /* PTRACE_??? */, 22210, 0x3ffffdb14c0, 0x1) = 0
ptrace(0x5001 /* PTRACE_??? */, 22210, 0x3ffffdb14c0, 0xbc1cbf28) = -1 EINVAL
(Invalid argument)
Couldn't write registers: Invalid argument.
Target is executing.
ptrace(PTRACE_KILL, 22210, 0, 0)        = 0
--- SIGCHLD (Child exited) @ 0 (0) ---
ptrace(PTRACE_KILL, 22210, 0, 0)        = -1 ESRCH (No such process)
(sid_s390x-dchroot)sbronson@zelenka:~/strace-code$ gdb --version
GNU gdb (GDB) 7.6.1 (Debian 7.6.1-1)
.
.
.

(The failing request is a PTRACE_POKEUSR_AREA request.)

The kernel package can be obtained from:
http://snapshot.debian.org/package/linux/3.2.51-1/#linux-image-3.2.0-4-s390x_3.2.51-1

(In this case, since the outer system is running the s390 arch, it came from
the _s390.deb)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug gdb/16468] gdb fails on s390x with "Couldn't write registers: Invalid argument"

[naesten at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16468

Samuel Bronson <naesten at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                URL|                            |http://bugs.debian.org/7287
                   |                            |05

--- Comment #1 from Samuel Bronson <naesten at gmail dot com> ---
Oh yeah, I forgot to mention: this is <http://bugs.debian.org/728705>.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug gdb/16468] gdb fails on s390x with "Couldn't write registers: Invalid argument"

[naesten at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16468

Samuel Bronson <naesten at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Target|                            |s390x-linux-gnu
                URL|http://bugs.debian.org/7287 |
                   |05                          |
               Host|                            |s390x-linux-gnu
           See Also|                            |http://bugs.debian.org/7287
                   |                            |05

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug gdb/16468] gdb fails on s390x with "Couldn't write registers: Invalid argument"

[naesten at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16468

Samuel Bronson <naesten at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |critical

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug gdb/16468] gdb fails on s390x with "Couldn't write registers: Invalid argument"

[naesten at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16468

--- Comment #2 from Samuel Bronson <naesten at gmail dot com> ---
Also, should you want to play around on zelenka.debian.org yourself, it
shouldn't be a problem to get you a guest account.  See
<https://dsa.debian.org/doc/guest-account/>; I believe Héctor Orón Martínez
<zumbi@debian.org> would be happy to sponsor any reputable upstream developer.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-15096-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Jan 23 01:15:33 2014
Return-Path: <gdb-prs-return-15096-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 23301 invoked by alias); 23 Jan 2014 01:15:33 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 23255 invoked by uid 48); 23 Jan 2014 01:15:29 -0000
From: "teawater at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/16494] Call-style dprintf does not work with
 disconnected-dprintf
Date: Thu, 23 Jan 2014 01:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: breakpoints
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: teawater at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: teawater at gmail dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc assigned_to
Message-ID: <bug-16494-4717-n2nBAG7MCG@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-16494-4717@http.sourceware.org/bugzilla/>
References: <bug-16494-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-q1/txt/msg00104.txt.bz2
Content-length: 470

https://sourceware.org/bugzilla/show_bug.cgi?id\x16494

teawater <teawater at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |teawater at gmail dot com
           Assignee|unassigned at sourceware dot org   |teawater at gmail dot com

--
You are receiving this mail because:
You are on the CC list for the bug.

[Bug gdb/16468] gdb fails on s390x with "Couldn't write registers: Invalid argument"

[sergiodj at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16468

Sergio Durigan Junior <sergiodj at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sergiodj at redhat dot com

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug gdb/16468] gdb fails on s390x with "Couldn't write registers: Invalid argument"

[naesten at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16468

--- Comment #3 from Samuel Bronson <naesten at gmail dot com> ---
Oh, by the way, as this is reported to work on other systems that are running
more recent kernel versions, it's quite possible that this is actually a
problem with zelenka's kernel, which turns out to just be the one in Debian
stable (codenamed wheezy).

Of course, if this is the case, it would be most helpful if you could help us
figure out *what* is wrong with this kernel so we can get it fixed in wheezy. 
I believe the offending code would be in
<http://sources.debian.net/src/linux/3.2.51-1/arch/s390/kernel/ptrace.c>, most
likely in the region starting at
<http://sources.debian.net/src/linux/3.2.51-1/arch/s390/kernel/ptrace.c#L250>
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug gdb/16468] gdb fails on s390x with "Couldn't write registers: Invalid argument"

[sergiodj at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16468

--- Comment #4 from Sergio Durigan Junior <sergiodj at redhat dot com> ---
(In reply to Samuel Bronson from comment #3)
> Oh, by the way, as this is reported to work on other systems that are
> running more recent kernel versions, it's quite possible that this is
> actually a problem with zelenka's kernel, which turns out to just be the one
> in Debian stable (codenamed wheezy).

Yeah, I have this strong feeling that the Linux kernel is the culprit here.

Anyway, unfortunately I won't have time to investigate this issue in the next 2
weeks.  I'll get back to it as soon as I can.

Thanks.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug gdb/16468] gdb fails on s390x with "Couldn't write registers: Invalid argument"

[naesten at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16468

Samuel Bronson <naesten at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #5 from Samuel Bronson <naesten at gmail dot com> ---
After further investigation, I reassigned this to the kernel in Debian, and I'm
marking it INVALID here.

Not sure exactly what the kernel is screwing up yet, though.

For the curious, details are at:
http://bugs-master.debian.org/cgi-bin/bugreport.cgi?bug=728705#47

-- 
You are receiving this mail because:
You are on the CC list for the bug.