public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "maarten at treewalker dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/14523] [MIPS] unexpected signal with gdb target
Date: Wed, 29 Aug 2012 20:58:00 -0000	[thread overview]
Message-ID: <bug-14523-4717-9BwvmzQ7vj@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14523-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=14523

Maarten ter Huurne <maarten at treewalker dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |maarten at treewalker dot
                   |                            |org

--- Comment #3 from Maarten ter Huurne <maarten at treewalker dot org> 2012-08-29 20:58:18 UTC ---
The problem was introduced between 7.3 and 7.4, to be exact in commit 7ade46b0
in the official git mirror, a change set by Ulrich Weigand committed on Wed Apr
27 13:29:11 2011 +0000.

On some platforms, such as Linux MIPS, NSIG is 128 and SIGRTMAX is also 128.
However, there is no GDB_SIGNAL_REALTIME_128 constant, so target signal 128 is
considered a real-time signal but not mappable to a GDB signal, which triggers
the error condition in gdb_signal_from_host() in gdb/common/signals.c.

I worked around the problem by mapping signal 128 to GDB_SIGNAL_UNKNOWN. See
attached patch. I don't know if this can be considered a solution or whether
introducing GDB_SIGNAL_REALTIME_128 would be preferred instead.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2012-08-29 20:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-27 10:29 [Bug gdb/14523] New: " dark_footix at yahoo dot fr
2012-08-27 18:02 ` [Bug gdb/14523] " eager at eagercon dot com
2012-08-28  9:46 ` dark_footix at yahoo dot fr
2012-08-29 20:58 ` maarten at treewalker dot org [this message]
2012-08-29 21:01 ` maarten at treewalker dot org
2012-09-04  7:57 ` dark_footix at yahoo dot fr
2013-05-28 14:45 ` james at albanarts dot com
2013-06-28 22:09 ` james.hogan at imgtec dot com
2013-07-01 12:29 ` sergiodj at redhat dot com
2013-07-01 12:36 ` sergiodj at redhat 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-14523-4717-9BwvmzQ7vj@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).