Hi,
thanks to a fix for Peter
([EMAIL PROTECTED])
I could build gdb-cvs two weeks ago ( on my IRIX 6.5 box)
But with the current cvs version I get
GDB bug: target.c (target_signal_from_host): unrecognized real-time signal
when gdb is about to stop at the first breakpoint.
Restoring the old version of target.[ch] it does work again.
I'll attach the diffs, the .NEW ones are the current cvs versions
which don't work.
Thanks for looking into it.
--
Helmut Jarausch
Lehrstuhl fuer Numerische Mathematik
Institute of Technology, RWTH Aachen
D 52056 Aachen, Germany
*** target.c.NEW Mon Oct 30 10:17:55 2000
--- target.c Mon Oct 30 19:20:47 2000
***************
*** 1424,1430 ****
{"SIG61", "Real-time event 61"},
{"SIG62", "Real-time event 62"},
{"SIG63", "Real-time event 63"},
! {"SIGCANCEL", "LWP internal signal"},
{"SIG32", "Real-time event 32"},
#if defined(MACH) || defined(__MACH__)
--- 1424,1431 ----
{"SIG61", "Real-time event 61"},
{"SIG62", "Real-time event 62"},
{"SIG63", "Real-time event 63"},
! {"SIG64", "Real-time event 64"},
! {"SIGCANCEL", "LWP internal signal"},
{"SIG32", "Real-time event 32"},
#if defined(MACH) || defined(__MACH__)
***************
*** 1740,1745 ****
--- 1741,1748 ----
if (33 <= hostsig && hostsig <= 63)
return (enum target_signal)
(hostsig - 33 + (int) TARGET_SIGNAL_REALTIME_33);
+ else if (hostsig == 64)
+ return TARGET_SIGNAL_REALTIME_64;
else
error ("GDB bug: target.c (target_signal_from_host): unrecognized real-time
signal");
}
***************
*** 2011,2016 ****
--- 2014,2021 ----
if (retsig >= SIGRTMIN && retsig <= SIGRTMAX)
return retsig;
}
+ else if (oursig == TARGET_SIGNAL_REALTIME_64)
+ return 64;
#endif
*oursig_ok = 0;
return 0;
***************
*** 2076,2082 ****
signal. The idea is to keep these circumstances limited so that
users (and scripts) develop portable habits. For comparison,
POSIX.2 `kill' requires that 1,2,3,6,9,14, and 15 work (and using a
! numeric signal at all is obsolescent. We are slightly more
lenient and allow 1-15 which should match host signal numbers on
most systems. Use of symbolic signal names is strongly encouraged. */
--- 2081,2087 ----
signal. The idea is to keep these circumstances limited so that
users (and scripts) develop portable habits. For comparison,
POSIX.2 `kill' requires that 1,2,3,6,9,14, and 15 work (and using a
! numeric signal at all is obscelescent. We are slightly more
lenient and allow 1-15 which should match host signal numbers on
most systems. Use of symbolic signal names is strongly encouraged. */
*** target.h.NEW Wed Oct 25 11:19:12 2000
--- target.h Fri Sep 29 15:05:57 2000
***************
*** 239,244 ****
--- 239,245 ----
of the protocol. Note that in some GDB's TARGET_SIGNAL_REALTIME_32
is number 76. */
TARGET_SIGNAL_REALTIME_32,
+ TARGET_SIGNAL_REALTIME_64,
#if defined(MACH) || defined(__MACH__)
/* Mach exceptions */
