This is the mail archive of the 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]

[testsuite, patch] can_single_step_to_signal_handler returns 0 on target tic6x-*-*

We are using software single-step on tic6x port, so unable to
single-step to signal handler.  Let can_single_step_to_signal_handler
return 0 if target is "tic6x-*-*".

Without this patch, gdb.base/kill-after-signal.exp fail on c6x-uclinux,

  FAIL: gdb.base/kill-after-signal.exp: stepi (timeout)
  FAIL: gdb.base/kill-after-signal.exp: kill (timeout)

With this patch applied, gdb.base/kill-after-signal.exp is UNTESTED.

It is obvious, committed.

Yao (éå) 
	* lib/gdb.exp (can_single_step_to_signal_handler): Return 0 when
	target is tic6x-*-*.

diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index 1476c19..644d14c 100644
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -1536,7 +1536,8 @@ proc can_single_step_to_signal_handler {} {
     # a signal is delivered during software single step, gdb is unable
     # to determine the next instruction addresses, because start of signal
     # handler is one of them.
-    if { [istarget "arm*-*-*"] || [istarget "mips*-*-*"] } {
+    if { [istarget "arm*-*-*"] || [istarget "mips*-*-*"]
+	 || [istarget "tic6x-*-*"] } {
 	return 0

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