public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Simon Marchi <simark@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] gdb: call gdb_tilde_expand instead of gdb_tilde_expand_up in source_script_with_search Date: Mon, 18 Apr 2022 20:12:34 +0000 (GMT) [thread overview] Message-ID: <20220418201234.3E4CC3858D1E@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=e0c34637019b0a070780b57b50d9026c0aca16f4 commit e0c34637019b0a070780b57b50d9026c0aca16f4 Author: Simon Marchi <simon.marchi@polymtl.ca> Date: Wed Apr 13 20:03:18 2022 -0400 gdb: call gdb_tilde_expand instead of gdb_tilde_expand_up in source_script_with_search This removes a use of gdb_tilde_expand_up, which is removed later in this series. Change-Id: I5887d526cea987103e4ca24514a982b0a28e992a Diff: --- 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 424a8740706..2b4becc97b2 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); }
reply other threads:[~2022-04-18 20:12 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220418201234.3E4CC3858D1E@sourceware.org \ --to=simark@sourceware.org \ --cc=gdb-cvs@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: linkBe 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).