From: Tom de Vries <tdevries@suse.de>
To: dwz@sourceware.org, jakub@redhat.com
Subject: [committed] Add dwz.sh test-case
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <20190316200834.GA18643@delia> (raw)
Hi,
Add test-case that uses dwz as input to dwz. We need a seperate executable
dwz-for-test because dwz itself may have been build without debug info.
Committed to trunk.
Thanks,
- Tom
Add dwz.sh test-case
2019-03-16 Tom de Vries <tdevries@suse.de>
* Makefile (TEST_EXECS): Add dwz-for-test.
(dwz-for-test): New target.
* testsuite/dwz.tests/dwz.sh: New test.
---
Makefile | 6 +++++-
testsuite/dwz.tests/dwz.sh | 7 +++++++
2 files changed, 12 insertions(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index f45bd40..d2aa386 100644
--- a/Makefile
+++ b/Makefile
@@ -18,7 +18,7 @@ clean:
PWD:=$(shell pwd -P)
TEST_SRC = $(PWD)/testsuite/dwz.tests
-TEST_EXECS = hello dw2-restrict py-section-script
+TEST_EXECS = hello dw2-restrict py-section-script dwz-for-test
hello:
$(CC) $(TEST_SRC)/hello.c -o $@ -g
@@ -29,6 +29,10 @@ dw2-restrict:
py-section-script:
$(CC) $(TEST_SRC)/py-section-script.s -o $@ -g || touch $@
+dwz-for-test:
+ $(CC) $(patsubst \.o$,.c,$(OBJECTS)) -O2 -g -w -lelf -o $@ -W \
+ -D_FILE_OFFSET_BITS=64 -DDWZ_VERSION='"for-test"'
+
# On some systems we need to set and export DEJAGNU to suppress
# WARNING: Couldn't find the global config file.
DEJAGNU ?= /dev/null
diff --git a/testsuite/dwz.tests/dwz.sh b/testsuite/dwz.tests/dwz.sh
new file mode 100644
index 0000000..ed49006
--- /dev/null
+++ b/testsuite/dwz.tests/dwz.sh
@@ -0,0 +1,7 @@
+cp ../dwz-for-test 1
+
+dwz 1
+
+smaller-than.sh 1 ../dwz-for-test
+
+rm -f 1
reply other threads:[~2019-03-16 20:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190316200834.GA18643@delia \
--to=tdevries@suse.de \
--cc=dwz@sourceware.org \
--cc=jakub@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).