patch to ignore SIGPWR and SIGXCPU (used by pthreads)

[Per Bothner <per@bothner.com>]

[-- Attachment #1: Type: text/plain, Size: 322 bytes --]

Ok to check in?  Without it, people debugging Java have to issue handle
commands, as shown in http://gcc.gnu.org/java/gdb.html.

	* infrun.c (_initialize_infrun):  Don't stop or print SIGCPU and
	SIGPWR - they are used by the Java runtime's thread support.
-- 
	--Per Bothner
per@bothner.com   http://www.bothner.com/per/

[-- Attachment #2: infrun.patch --]
[-- Type: text/plain, Size: 949 bytes --]

	* infrun.c (_initialize_infrun):  Don't stop or print SIGCPU and
	SIGPWR - they are used by the Java runtime's thread support.

Index: infrun.c
===================================================================
RCS file: /cvs/src/src/gdb/infrun.c,v
retrieving revision 1.50
diff -u -p -r1.50 infrun.c
--- infrun.c	2002/01/17 22:15:17	1.50
+++ infrun.c	2002/01/19 20:17:19
@@ -4298,6 +4298,12 @@ of the program stops.", &cmdlist);
   signal_stop[TARGET_SIGNAL_WINCH] = 0;
   signal_print[TARGET_SIGNAL_WINCH] = 0;
 
+  /* These are used for pthread context switching, used by libgcj. */
+  signal_stop[TARGET_SIGNAL_PWR] = 0;
+  signal_print[TARGET_SIGNAL_PWR] = 0;
+  signal_stop[TARGET_SIGNAL_XCPU] = 0;
+  signal_print[TARGET_SIGNAL_XCPU] = 0;
+
   /* These signals are used internally by user-level thread
      implementations.  (See signal(5) on Solaris.)  Like the above
      signals, a healthy program receives and handles them as part of