This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug gdb/14523] [MIPS] unexpected signal with gdb target


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]