public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed
From: "jirislaby at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/24275] hardlink handling leaves temporary file if not file compressed
Date: Fri, 02 Oct 2020 04:09:16 +0000	[thread overview]
Message-ID: <bug-24275-11298-InFGioWTXj@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24275-11298@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=24275

Jiri Slaby <jirislaby at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jirislaby at gmail dot com

--- Comment #5 from Jiri Slaby <jirislaby at gmail dot com> ---
(In reply to Tom de Vries from comment #4)
> Neither, I just didn't plan this for the upcoming release, but for the one
> after that.

So what about now? It still triggers, currently it bites perf in openSUSE, see
bug 26645 and
https://build.opensuse.org/package/view_file/openSUSE:Factory/perf/perf.spec?expand=1:
# a bug in dwz leaves temporary trace-*.debug.#dwz#.* on 64 bits in place
# remove this once fixed, see:
# https://sourceware.org/bugzilla/show_bug.cgi?id=26645
%define _find_debuginfo_dwz_opts %{nil}

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

  parent reply	other threads:[~2020-10-02  4:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-01  0:00 [Bug default/24275] New: " vries at gcc dot gnu.org
2019-01-01  0:00 ` [Bug default/24275] " vries at gcc dot gnu.org
2019-01-01  0:00 ` vries at gcc dot gnu.org
2020-01-01  0:00 ` vries at gcc dot gnu.org
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 [this message]
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 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-24275-11298-InFGioWTXj@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).