[patch] [ppc64] testsuite: break-interp.exp [Re: info files' Entry point on ppc64]

[Jan Kratochvil <jan.kratochvil@redhat.com>]

On Wed, 08 Sep 2010 18:36:55 +0200, Edjunior Barbosa Machado wrote:
>         Entry point: 0x251c11e0
> break *0x251c11e0
> Program received signal SIGSEGV, Segmentation fault.
> 0x7d821008251b0a90 in ?? ()

OK, thanks for the bugreport, fix attached.

OTOH still both ppc64->ppc32 and ppc64->ppc64 produce a lot of FAILs which
I do not see obvious (such as some `seen displacement message as ZERO' which
should have 0 displacement as being prelinked); I can check them later.


Regards,
Jan


gdb/testsuite/
2010-09-09  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.base/break-interp.exp (reach): Permit leading . for ppc64.
	(test_ld) <powerpc64-*>: New.

--- a/gdb/testsuite/gdb.base/break-interp.exp
+++ b/gdb/testsuite/gdb.base/break-interp.exp
@@ -136,10 +136,10 @@ proc reach {func command displacement} {
 		}
 		exp_continue
 	    }
-	    -re "Breakpoint \[0-9\]+, $func \\(.*\\) at .*:\[0-9\]+\r\n.*$gdb_prompt $" {
+	    -re "Breakpoint \[0-9\]+, \\.?$func \\(.*\\) at .*:\[0-9\]+\r\n.*$gdb_prompt $" {
 		pass $test
 	    }
-	    -re "Breakpoint \[0-9\]+, \[0-9xa-f\]+ in $func \\(\\).*\r\n$gdb_prompt $" {
+	    -re "Breakpoint \[0-9\]+, \[0-9xa-f\]+ in \\.?$func \\(\\).*\r\n$gdb_prompt $" {
 		pass $test
 	    }
 	}
@@ -399,6 +399,17 @@ proc test_ld {file ifmain trynosym displacement} {
 		pass $test
 	    }
 	}
+	# `info sym' cannot be tested for .opd as the binary may not have
+	# symbols.
+	if [istarget powerpc64-*] {
+	    set test "convert entry point"
+	    gdb_test_multiple "p *(void(*)(void) *) 0x$entrynohex" $test {
+		-re " =( \\(\[^0-9\]*\\))? 0x(\[0-9a-f\]+)( < \[^\r\n\]*)?\r\n$gdb_prompt $" {
+		    set entrynohex $expect_out(2,string)
+		    pass $test
+		}
+	    }
+	}
 	if {$entrynohex != ""} {
 	    gdb_test "break *0x$entrynohex" "" "break at entry point"
 	    gdb_test "continue" "\r\nBreakpoint \[0-9\]+, 0x0*$entrynohex in .*" "entry point reached"