public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "sergiodj at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/14523] [MIPS] unexpected signal with gdb target
Date: Mon, 01 Jul 2013 12:36:00 -0000	[thread overview]
Message-ID: <bug-14523-4717-v46MQdzt66@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14523-4717@http.sourceware.org/bugzilla/>

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

--- Comment #8 from Sergio Durigan Junior <sergiodj at redhat dot com> ---
For the record, I have submitted a patch series which touches this code, and
will likely cause the bug to reappear.  The link to the specific MIPS patch is:

<http://sourceware.org/ml/gdb-patches/2013-07/msg00014.html>

I was strongly considering incrementing GDB's internal signal representation to
accommodate the 128th realtime signal, and after reading this bug my
willingness became stronger.  I will keep posting updates to this bug as I
discuss the matter with the community.

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


      parent reply	other threads:[~2013-07-01 12:36 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
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 [this message]

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-v46MQdzt66@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).