Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb/testsuite] Add KFAIL for missing support of reverse-debugging xsave
Date: Sat, 12 Oct 2019 23:09:00 -0000	[thread overview]
Message-ID: <558367f403dfa6290ed40b06382b45dc@polymtl.ca> (raw)
In-Reply-To: <20190927151128.GA29080@delia>

On 2019-09-27 11:11, Tom de Vries wrote:
> Hi,
> 
> Normally the gdb.reverse/*.exp test-cases pass on my system (apart from 
> the
> record/23188 KFAIL for gdb.reverse/step-precsave.exp).  But when 
> specifying
> GLIBC_TUNABLES=glibc.tune.hwcaps=-XSAVEC_Usable to force glibc to use
> _dl_runtime_resolve_xsave instead of _dl_runtime_resolve_xsavec, we run 
> into
> 1054 FAILs like this:
> ...
> (gdb) PASS: gdb.reverse/sigall-reverse.exp: b gen_HUP
> continue^M
> Continuing.^M
> Process record does not support instruction 0xfae64 at address \
>   0x7ffff7ded958.^M
> Process record: failed to record execution log.^M
> ^M
> Program stopped.^M
> 0x00007ffff7ded958 in _dl_runtime_resolve_xsave () from \
>   /lib64/ld-linux-x86-64.so.2^M
> (gdb) FAIL: gdb.reverse/sigall-reverse.exp: get signal ABRT
> ...
> 
> The problem is that the xsave instruction is not supported in
> reverse-debugging (PR record/25038).
> 
> Add KFAILs for this PR.
> 
> Tested on x86_64-linux.
> 
> OK for trunk?

Hi Tom,

That looks good to me in general.  Just one note here:

> @@ -289,8 +295,12 @@ set sig_supported 1
>  set thissig "ABRT"
> 
>  # test signal handling
> +set record_instruction_kfail 0
>  foreach sig [lrange $signals 1 end] {
>      test_one_sig $sig
> +    if { $record_instruction_kfail } {
> +	return -1
> +    }

It seems like record_instruction_kfail is never set in this file, 
sigall-precsave.exp, I suppose it should?

Simon


  parent reply	other threads:[~2019-10-12 23:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-27 15:11 Tom de Vries
2019-10-12 16:24 ` [PING][PATCH][gdb/testsuite] " Tom de Vries
2019-10-12 23:09 ` Simon Marchi [this message]
2019-10-13  0:59   ` [PATCH][gdb/testsuite] " Tom de Vries

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=558367f403dfa6290ed40b06382b45dc@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    /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