diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index ecb008e966..e78e42776f 100644
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,3 +1,9 @@
+2004-08-08  Daniel Jacobowitz  <dan@debian.org>
+
+	PR gdb/1738
+	* gdb.base/signals.exp (signal_tests_1): KFAIL bug in continuing
+	from a breakpoint with a pending signal.
+
 2004-08-08  Daniel Jacobowitz  <dan@debian.org>
 
 	PR gdb/1736
diff --git a/gdb/testsuite/gdb.base/signals.exp b/gdb/testsuite/gdb.base/signals.exp
index 803ee78e37..09354a2e0c 100644
--- a/gdb/testsuite/gdb.base/signals.exp
+++ b/gdb/testsuite/gdb.base/signals.exp
@@ -114,9 +114,24 @@ proc signal_tests_1 {} {
 	# In running to func2, the 2rd alarm call will have been set
 	# up, let it be delivered.
 
+	# This doesn't work correctly on platforms with hardware single
+	# step...
+
 	sleep 2
+
+	setup_kfail "i*86-*-*" gdb/1738
+	setup_kfail "x86_64-*-*" gdb/1738
+	setup_kfail "rs6000-*-*" gdb/1738
+	setup_kfail "powerpc-*-*" gdb/1738
+	setup_kfail "sparc-*-*" gdb/1738
 	gdb_test "continue" "Breakpoint.*handler.*" \
 	    "continue to handler for 3rd alarm call"
+
+	setup_kfail "i*86-*-*" gdb/1738
+	setup_kfail "x86_64-*-*" gdb/1738
+	setup_kfail "rs6000-*-*" gdb/1738
+	setup_kfail "powerpc-*-*" gdb/1738
+	setup_kfail "sparc-*-*" gdb/1738
 	gdb_test "backtrace" \
 	    "#0  handler.*#1.*signal handler called.*#2  func2.*#3.*main.*" \
 	    "backtrace for 3rd alarm"