Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Andreas Arnez <arnez@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org,
	Sergio Durigan Junior <sergiodj@redhat.com>,
	       Ulrich Weigand <uweigand@de.ibm.com>,
	       Andreas Krebbel <krebbel@linux.vnet.ibm.com>,
	       Yao Qi <yao@codesourcery.com>
Subject: Re: [PATCH] Fix regression on s390x with entry-values.exp
Date: Mon, 13 Jan 2014 16:57:00 -0000	[thread overview]
Message-ID: <52D41AE6.8000005@redhat.com> (raw)
In-Reply-To: <87a9ez4yuc.fsf@br87z6lw.de.ibm.com>

On 01/13/2014 04:43 PM, Andreas Arnez wrote:
> The trace-specific test case 'entry-values' concludes fairly late in the
> process that this platform doesn't support trace.  Before that, there
> are some platform specifics that don't work on s390x.  The fix below
> addresses two aspects:
> 
> * Removal of an excess space character in the regex for the disassembly.
>   This is needed when there is a function alignment gap, because then
>   the hex address is immediately followed by a colon.

Looks good to me, but can you paste/add the relevant disassemble
snippet from the gdb.log, in the commit log?  A picture is worth a
thousand words.

> * Handling for the s390-specific call instruction.
> 
> --
> testsuite/ChangeLog
> 2014-01-13  Andreas Arnez  <arnez@linux.vnet.ibm.com>
> 
> 	* gdb.trace/entry-values.exp: Remove excess space character from
> 	regex patterns.  Handle s390 call instruction.
> 
> 
> Modified gdb/testsuite/gdb.trace/entry-values.exp
> diff --git a/gdb/testsuite/gdb.trace/entry-values.exp b/gdb/testsuite/gdb.trace/entry-values.exp
> index 0fb35a0..f10ffa6 100644
> --- a/gdb/testsuite/gdb.trace/entry-values.exp
> +++ b/gdb/testsuite/gdb.trace/entry-values.exp
> @@ -57,7 +57,7 @@ gdb_test_multiple $test $test {
>  
>  set test "disassemble foo+$foo_length,+10"
>  gdb_test_multiple $test $test {
> -    -re ".*($hex) <foo\\+$foo_length>:\[^\r\n\]+\r\n\[ \]+($hex) .*\.\r\n$gdb_prompt $" {
> +    -re ".*($hex) <foo\\+$foo_length>:\[^\r\n\]+\r\n\[ \]+($hex).*\.\r\n$gdb_prompt $" {
>  	set start $expect_out(1,string)
>  	set end $expect_out(2,string)
>  
> @@ -77,6 +77,8 @@ set bar_call_foo ""
>  
>  if { [istarget "arm*-*-*"] || [istarget "aarch64*-*-*"] } {
>      set call_insn "bl"
> +} elseif { [istarget "s390*-*-*"] } {
> +    set call_insn "brasl"
>  } else {
>      set call_insn "call"
>  }
> @@ -109,7 +111,7 @@ if { [string equal $bar_call_foo ""] || [string equal $bar_length ""] } {
>  
>  set test "disassemble bar+$bar_length,+10"
>  gdb_test_multiple $test $test {
> -    -re ".*($hex) <bar\\+$bar_length>:\[^\r\n\]+\r\n\[ \]+($hex) .*\.\r\n$gdb_prompt $" {
> +    -re ".*($hex) <bar\\+$bar_length>:\[^\r\n\]+\r\n\[ \]+($hex).*\.\r\n$gdb_prompt $" {
>  	set start $expect_out(1,string)
>  	set end $expect_out(2,string)
>  
> 


-- 
Pedro Alves


  reply	other threads:[~2014-01-13 16:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13 16:43 Andreas Arnez
2014-01-13 16:57 ` Pedro Alves [this message]
2014-01-22 16:15 ` Andreas Krebbel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52D41AE6.8000005@redhat.com \
    --to=palves@redhat.com \
    --cc=arnez@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=krebbel@linux.vnet.ibm.com \
    --cc=sergiodj@redhat.com \
    --cc=uweigand@de.ibm.com \
    --cc=yao@codesourcery.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox