From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/24277] New: dwz needs testsuite
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <bug-24277-11298@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=24277
Bug ID: 24277
Summary: dwz needs testsuite
Product: dwz
Version: unspecified
Status: NEW
Severity: enhancement
Priority: P2
Component: default
Assignee: nobody at sourceware dot org
Reporter: vries at gcc dot gnu.org
CC: dwz at sourceware dot org
Target Milestone: ---
With dwz bugs like:
- PR24274 "low-mem files processed in multifile mode"
- PR24275 "hardlink handling leaves temporary file if not file compressed"
it becomes clear that we need a dwz testsuite, to:
- be able to add tests to patches fixing those PRs to verify that they're fixed
- check that patches fixing those PRs don't break other behaviour
The gdb testsuite contains two dwz test modes in conjunction with
target_board=cc-with-tweaks:
- CC_WITH_TWEAKS_FLAGS='-z' (regular dwz)
- CC_WITH_TWEAKS_FLAGS='-m' ()
but that tests just the dwarf output, and uses dwz in a limited amount of ways.
It's debatable whether we want to add (possibly large) executables to the
testsuite to test assert fixes which are typically not triggered with hello
world type examples.
But adding hello world type examples should be possible, and for that we need
some testsuite infrastructure.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-02-27 13:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 vries at gcc dot gnu.org [this message]
2019-01-01 0:00 ` [Bug default/24277] " mark at klomp dot org
2019-01-01 0:00 ` vries at gcc dot gnu.org
2019-01-01 0:00 ` jakub at redhat dot com
2019-01-01 0:00 ` vries at gcc dot gnu.org
2019-01-01 0:00 ` vries at gcc dot gnu.org
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=bug-24277-11298@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=dwz@sourceware.org \
/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).