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

Edjunior Barbosa Machado emachado@linux.vnet.ibm.com
Fri Sep 10 14:55:00 GMT 2010



On 09/09/2010 11:05 AM, Jan Kratochvil wrote:
> 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.
>
Hi Jan,

thanks for the patch, but it seems it doesn't work properly when testing 32-bit gdb in a 64-bit environment. Using is_lp64_target should avoid this issue.

Thanks,
--
Edjunior Barbosa Machado
IBM Linux Technology Center




gdb/testsuite/

2010-09-10  Edjunior Barbosa Machado  <emachado@linux.vnet.ibm.com>



	* gdb.base/break-interp.exp: add is_lp64_target to check 64bit target



--- a/gdb/testsuite/gdb.base/break-interp.exp
+++ b/gdb/testsuite/gdb.base/break-interp.exp
@@ -401,7 +401,7 @@ proc test_ld {file ifmain trynosym displacement} {
  	}
  	# `info sym' cannot be tested for .opd as the binary may not have
  	# symbols.
-	if [istarget powerpc64-*] {
+	if {[istarget powerpc64-*] && [is_lp64_target]} {
  	    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 $" {



More information about the Gdb mailing list