From: Simon Marchi <simon.marchi@polymtl.ca>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: [PATCH 4/5] gdb: use gdb_tilde_expand instead of gdb_tilde_expand_up in source_script_with_search
Date: Thu, 14 Apr 2022 16:01:36 -0400 [thread overview]
Message-ID: <20220414200137.3479373-4-simon.marchi@polymtl.ca> (raw)
In-Reply-To: <20220414200137.3479373-1-simon.marchi@polymtl.ca>
From: Simon Marchi <simon.marchi@efficios.com>
Since this is the latest use of gdb_tilde_expand_up, remove it.
Change-Id: I964c812ce55fe087876abf91e7a3577ad79c0425
---
gdbsupport/gdb_tilde_expand.cc | 9 ---------
gdbsupport/gdb_tilde_expand.h | 4 ----
2 files changed, 13 deletions(-)
diff --git a/gdbsupport/gdb_tilde_expand.cc b/gdbsupport/gdb_tilde_expand.cc
index e3f9308a14f0..177d296a14fd 100644
--- a/gdbsupport/gdb_tilde_expand.cc
+++ b/gdbsupport/gdb_tilde_expand.cc
@@ -102,12 +102,3 @@ gdb_tilde_expand (const char *dir)
gdb_assert (glob.pathc () == 1);
return std::string (glob.pathv ()[0]) + remainder;
}
-
-/* See gdbsupport/gdb_tilde_expand.h. */
-
-gdb::unique_xmalloc_ptr<char>
-gdb_tilde_expand_up (const char *dir)
-{
- const std::string expanded = gdb_tilde_expand (dir);
- return make_unique_xstrdup (expanded.c_str ());
-}
diff --git a/gdbsupport/gdb_tilde_expand.h b/gdbsupport/gdb_tilde_expand.h
index c47cd6a214f7..06b96517697c 100644
--- a/gdbsupport/gdb_tilde_expand.h
+++ b/gdbsupport/gdb_tilde_expand.h
@@ -23,8 +23,4 @@
/* Perform tilde expansion on DIR, and return the full path. */
extern std::string gdb_tilde_expand (const char *dir);
-/* Same as GDB_TILDE_EXPAND, but return the full path as a
- gdb::unique_xmalloc_ptr<char>. */
-extern gdb::unique_xmalloc_ptr<char> gdb_tilde_expand_up (const char *dir);
-
#endif /* COMMON_GDB_TILDE_EXPAND_H */
--
2.35.2
next prev parent reply other threads:[~2022-04-14 20:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 20:01 [PATCH 1/5] gdb: call " Simon Marchi
2022-04-14 20:01 ` [PATCH 2/5] gdbsupport: make gdb_abspath return an std::string Simon Marchi
2022-04-18 19:41 ` Tom Tromey
2022-04-18 20:09 ` Pedro Alves
2022-04-18 20:11 ` Simon Marchi
2022-04-14 20:01 ` [PATCH 3/5] gdbsupport: make gdb_realpath_keepfile " Simon Marchi
2022-04-18 19:44 ` Tom Tromey
2022-04-14 20:01 ` Simon Marchi [this message]
2022-04-18 19:44 ` [PATCH 4/5] gdb: use gdb_tilde_expand instead of gdb_tilde_expand_up in source_script_with_search Tom Tromey
2022-04-18 20:12 ` Simon Marchi
2022-04-14 20:01 ` [PATCH 5/5] gdbsupport: add path_join function Simon Marchi
2022-04-15 5:59 ` Eli Zaretskii
2022-04-18 18:11 ` Simon Marchi
2022-04-18 18:30 ` Eli Zaretskii
2022-04-18 19:24 ` Pedro Alves
2022-04-15 14:38 ` Lancelot SIX
2022-04-15 16:55 ` Lancelot SIX
2022-04-18 18:43 ` Simon Marchi
2022-04-18 19:09 ` Pedro Alves
2022-04-18 19:12 ` Simon Marchi
2022-04-18 20:55 ` Simon Marchi
2022-04-18 21:07 ` Pedro Alves
2022-04-19 0:19 ` Simon Marchi
2022-04-18 19:22 ` Pedro Alves
2022-04-18 20:01 ` Tom Tromey
2022-04-18 23:11 ` Lancelot SIX
2022-04-20 0:22 ` Simon Marchi
2022-04-18 19:36 ` [PATCH 1/5] gdb: call gdb_tilde_expand instead of gdb_tilde_expand_up in source_script_with_search Tom Tromey
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=20220414200137.3479373-4-simon.marchi@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.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).