public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "naesten at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/16468] gdb fails on s390x with "Couldn't write registers: Invalid argument"
Date: Thu, 23 Jan 2014 22:56:00 -0000	[thread overview]
Message-ID: <bug-16468-4717-3onqZZFGFJ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16468-4717@http.sourceware.org/bugzilla/>

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.


  parent reply	other threads:[~2014-01-23 22:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20  2:46 [Bug gdb/16468] New: " naesten at gmail dot com
2014-01-20  2:49 ` [Bug gdb/16468] " naesten at gmail dot com
2014-01-21  1:37 ` naesten at gmail dot com
2014-01-21 21:28 ` naesten at gmail dot com
2014-01-22 19:17 ` naesten at gmail dot com
2014-01-23  1:45 ` sergiodj at redhat dot com
2014-01-23 22:56 ` naesten at gmail dot com [this message]
2014-01-26  5:35 ` sergiodj at redhat dot com
2014-02-01  0:45 ` naesten at gmail 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=bug-16468-4717-3onqZZFGFJ@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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).