public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25843] New: gdb-add-index uses temporary files alongside exec
Date: Fri, 17 Apr 2020 11:06:40 +0000 [thread overview]
Message-ID: <bug-25843-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=25843
Bug ID: 25843
Summary: gdb-add-index uses temporary files alongside exec
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
When running gdb-add-index on an executable:
...
$ mkdir bla
$ gcc hello.c -o bla/a.out -g
$ bash -x gdb-add-index bla/a.out 2>&1 | grep "trap"
+ trap 'rm -f bla/a.out.gdb-index bla/a.out.debug_names bla/a.out.debug_str
bla/a.out.debug_str.merge bla/a.out.debug_str.err' 0
...
we can see that a number of temporary files is used, located in the same
directory as the argument file.
It should probably use proper temporary files in a temp directory.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-04-17 11:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 11:06 vries at gcc dot gnu.org [this message]
2020-04-17 11:06 ` [Bug gdb/25843] " vries at gcc dot gnu.org
2023-12-10 15:37 ` tromey at sourceware dot 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-25843-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).