From: Simon Marchi <simon.marchi@polymtl.ca>
To: gdb-patches@sourceware.org
Subject: [PATCH 1/5] gdb: call gdb_tilde_expand instead of gdb_tilde_expand_up in source_script_with_search
Date: Thu, 14 Apr 2022 16:01:33 -0400 [thread overview]
Message-ID: <20220414200137.3479373-1-simon.marchi@polymtl.ca> (raw)
This removes a use of gdb_tilde_expand_up, which is removed later in
this series.
Change-Id: I5887d526cea987103e4ca24514a982b0a28e992a
---
gdb/cli/cli-cmds.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/gdb/cli/cli-cmds.c b/gdb/cli/cli-cmds.c
index 424a8740706c..2b4becc97b22 100644
--- a/gdb/cli/cli-cmds.c
+++ b/gdb/cli/cli-cmds.c
@@ -749,13 +749,13 @@ source_script_with_search (const char *file, int from_tty, int search_path)
this if we (may have) used search_path, as printing the full path in
errors for the non-search case can be more noise than signal. */
const char *file_to_open;
- gdb::unique_xmalloc_ptr<char> tilde_expanded_file;
+ std::string tilde_expanded_file;
if (search_path)
file_to_open = opened->full_path.get ();
else
{
- tilde_expanded_file = gdb_tilde_expand_up (file);
- file_to_open = tilde_expanded_file.get ();
+ tilde_expanded_file = gdb_tilde_expand (file);
+ file_to_open = tilde_expanded_file.c_str ();
}
source_script_from_stream (opened->stream.get (), file, file_to_open);
}
base-commit: 8e347faf8f1556a0f1afc33bd53099ec5f2f8efe
--
2.35.2
next 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 Simon Marchi [this message]
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 ` [PATCH 4/5] gdb: use gdb_tilde_expand instead of gdb_tilde_expand_up in source_script_with_search Simon Marchi
2022-04-18 19:44 ` 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-1-simon.marchi@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@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).