From: Ulf Hermann <ulf.hermann@qt.io>
To: Andreas Schwab <schwab@suse.de>, Mark Wielaard <mark@klomp.org>
Cc: elfutils-devel@sourceware.org
Subject: Re: [PATCH 2/2] run-strip-reloc.sh: Skip debug file check for riscv
Date: Tue, 17 Jul 2018 09:49:00 -0000 [thread overview]
Message-ID: <772c2011-e7d9-819f-bbfc-9625d28579dc@qt.io> (raw)
In-Reply-To: <mvm8t6a1a83.fsf@suse.de>
> What is the issue? The test worksforme.
The test only works because we keep the temporary files from the
previous runtest() call around. The hello_riscv64.ko run doesn't
overwrite the debug files, and instead checks the old ones again. That
"succeeds", but it's bogus.
My first patch removes all temporary files at the beginning of runtest()
which exposes this.
Ulf
next prev parent reply other threads:[~2018-07-17 9:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 10:02 Ulf Hermann
2018-07-16 22:01 ` Mark Wielaard
2018-07-17 9:29 ` Andreas Schwab
2018-07-17 9:49 ` Ulf Hermann [this message]
2018-07-17 10:06 ` Andreas Schwab
2018-07-17 10:05 ` Mark Wielaard
2018-07-17 10:09 ` Andreas Schwab
2018-07-17 10:33 ` Mark Wielaard
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=772c2011-e7d9-819f-bbfc-9625d28579dc@qt.io \
--to=ulf.hermann@qt.io \
--cc=elfutils-devel@sourceware.org \
--cc=mark@klomp.org \
--cc=schwab@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).