public inbox for
 help / color / mirror / Atom feed
From: "vries at gcc dot" <>
Subject: [Bug default/24275] New: hardlink handling leaves temporary file if not file compressed
Date: Tue, 01 Jan 2019 00:00:00 -0000	[thread overview]
Message-ID: <> (raw)

            Bug ID: 24275
           Summary: hardlink handling leaves temporary file if not file
           Product: dwz
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: default
          Assignee: nobody at sourceware dot org
          Reporter: vries at gcc dot
                CC: dwz at sourceware dot org
  Target Milestone: ---

[ Filed before at:
- rbc#1625780 - "dwz crashed on s390x and armv7hl and rpmbuild leave
- rbc#1671883 - "dwz fails to remove temporary files if input files are

Consider a hello world executable a.out:
$ gcc -g hello.c

with a hardlink b.out:
$ ln a.out b.out

Running dwz once (with hardlink support) compresses them:
$ dwz -h a.out b.out

and trying once more, doesn't compress them further:
$ dwz -h a.out b.out
dwz: a.out: DWARF compression not beneficial - old size 3452 new size 3452

but leaves a temporary file:
$ ls a.out* b.out*
a.out  b.out  b.out.#dwz#.uiIcPY

You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2019-02-27  9:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-01  0:00 vries at gcc dot [this message]
2019-01-01  0:00 ` [Bug default/24275] " vries at gcc dot
2019-01-01  0:00 ` vries at gcc dot
2020-01-01  0:00 ` vries at gcc dot
2020-01-01  0:00 ` jakub at redhat dot com
2020-10-01 13:19 ` mark at klomp dot org
2020-10-02  4:09 ` jirislaby at gmail dot com
2020-11-08 22:25 ` mark at klomp dot org
2021-02-13 22:57 ` mark at klomp dot org
2021-03-04  8:07 ` vries at gcc dot

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:

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

  git send-email \ \ \ \

* 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).