Discussion:
Bug#728705: gdb fails on s390x with "Couldn't write registers: Invalid argument"
(too old to reply)
Thibaut Paumard
2013-11-04 13:50:01 UTC
Permalink
Package: gdb
Version: 7.6.1-1
Severity: important
X-Debbugs-CC: debian-***@lists.debian.org

Dear Maintainer,

gdb seems to be completely useless on s390x. I tried running it against
various executables (both buggy and sane). gdb seems to launch the
executable, however the subprocess doesn't seem to be doing anything.
gdb just gives a message, but it does not even seem to consider the
situation fatal and just seats there, apparently considering that the
subprocess is running faultlessly. Example session on "echo foo", notice
how "foo" is not echoed:

________________ GDB SESSION _______________________

(sid_s390x-dchroot)***@zelenka:~$ gdb --args echo foo
GNU gdb (GDB) 7.6.1 (Debian 7.6.1-1)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "s390x-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /bin/echo...(no debugging symbols found)...done.
(gdb) run
Starting program: /bin/echo foo
Couldn't write registers: Invalid argument.
(gdb) bt
Target is executing.
(gdb) quit
A debugging session is active.

Inferior 1 [process 18228] will be killed.

Quit anyway? (y or n) y
(sid_s390x-dchroot)***@zelenka:~$

________________ END GDB SESSION _________________________


Kind regards, Thibaut.


-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: s390x

Kernel: Linux 3.2.0-4-s390x (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages gdb depends on:
ii gdbserver 7.6.1-1
ii libc6 2.17-93
ii libexpat1 2.1.0-4
ii liblzma5 5.1.1alpha+20120614-2
ii libncurses5 5.9+20130608-1
ii libpython2.7 2.7.5-8
ii libreadline6 6.2+dfsg-0.1
ii libtinfo5 5.9+20130608-1
ii zlib1g 1:1.2.8.dfsg-1

Versions of packages gdb recommends:
pn libc-dbg <none>

Versions of packages gdb suggests:
pn gdb-doc <none>

-- no debconf information
Vincent Bernat
2013-12-21 17:40:01 UTC
Permalink
Post by Thibaut Paumard
gdb seems to be completely useless on s390x. I tried running it against
various executables (both buggy and sane). gdb seems to launch the
executable, however the subprocess doesn't seem to be doing anything.
gdb just gives a message, but it does not even seem to consider the
situation fatal and just seats there, apparently considering that the
subprocess is running faultlessly. Example session on "echo foo", notice
I have the same problem and since the only s390x porterbox is hit by
this bug, this makes any serious debugging quite impossible for this
architecture.

If the current work-around is to have a more recent kernel, maybe we
could ask DSA to install a backported kernel?
--
Follow each decision as closely as possible with its associated action.
- The Elements of Programming Style (Kernighan & Plauger)
Loading...