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

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

[dark_footix at yahoo dot fr]

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

             Bug #: 14523
           Summary: [MIPS] unexpected signal with gdb target
           Product: gdb
           Version: 7.5
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
        AssignedTo: unassigned@sourceware.org
        ReportedBy: dark_footix@yahoo.fr
    Classification: Unclassified


Hi,

Native gdb on mipsel board crashes at startup with an "unexpected signal"
message 
( this issue is not reproduced with gdbserver mipsel . )

Could it be this fix ? I saw a discussion on a patch :

[PATCH] MIPS Linux signals
http://sources.redhat.com/ml/gdb-patches/2012-06/msg00041.html

 is it integrated ? is it a similar issue ?

If so, How can I download this fix ?  ( I am not user friendly of svn / cvs. if
you have detail , I am interested  ... )


Best Regards,
Frédéric

-- 
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.

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

[eager at eagercon dot com]

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

eager at eagercon dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |eager at eagercon dot com

--- Comment #1 from eager at eagercon dot com 2012-08-27 18:02:26 UTC ---
Patch mentioned only affects debugging core files, not use of gdbserver.

-- 
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.

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

[dark_footix at yahoo dot fr]

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

--- Comment #2 from Fred_gdb <dark_footix at yahoo dot fr> 2012-08-28 09:46:14 UTC ---
log error , 


# gdb /usr/bin/my_soft 
GNU gdb (GDB) 7.5.50.20120813
Copyright (C) 2012 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 "mipsel-linux-uclibc".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/my_soft ...done.
(gdb) r
Starting program: /usr/bin/my_soft 
GDB bug: target.c (gdb_signal_from_host): unrecognized real-time signal





This is not reproduced on gdb target 7.3 

It seems in gdb/common/signals.c , 
there was some code removed flagged in #ifndef GDBSERVER

-- 
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.

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

[maarten at treewalker dot org]

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.

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

[maarten at treewalker dot org]

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

--- Comment #4 from Maarten ter Huurne <maarten at treewalker dot org> 2012-08-29 21:00:53 UTC ---
Created attachment 6621
  --> http://sourceware.org/bugzilla/attachment.cgi?id=6621
Patch for gdb 7.5 to map signal 128 to GDB_SIGNAL_UNKNOWN

-- 
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.

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

[dark_footix at yahoo dot fr]

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

--- Comment #5 from Fred_gdb <dark_footix at yahoo dot fr> 2012-09-04 07:56:52 UTC ---
Perfect !

That's exactly fix my issue.

Thanks

-- 
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.

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

[james at albanarts dot com]

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

James Hogan <james at albanarts dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |james at albanarts dot com

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

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

[james.hogan at imgtec dot com]

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

James Hogan <james.hogan at imgtec dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|james at albanarts dot com         |james.hogan at imgtec dot com

--- Comment #6 from James Hogan <james.hogan at imgtec dot com> ---
The following commit in uClibc:

http://git.uclibc.org/uClibc/commit/?id=2da958760f798224065508431787e3a83b7fe2ae

Should prevent this problem from occurring after gdb is rebuilt against it.
uClibc now matches glibc in defining __SIGRTMAX=127 instead of 128.

Of course whether gdb should still understand SIG128 is a different question
(since SIG128 has existed until now).

Cheers
James

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

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

[sergiodj at redhat dot com]

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

Sergio Durigan Junior <sergiodj at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sergiodj at redhat dot com

--- Comment #7 from Sergio Durigan Junior <sergiodj at redhat dot com> ---
The following patch is being discussed in the Linux kernel.

<http://www.mail-archive.com/stable@vger.kernel.org/msg45489.html>

It is related to this issue.

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

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

[sergiodj at redhat dot com]

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.