public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Tom Tromey <tromey@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] Remove unnecessary line from catch_exec_command_1 Date: Fri, 6 May 2022 18:10:41 +0000 (GMT) [thread overview] Message-ID: <20220506181041.D3AF4395201B@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=fb9e63701335b7383622e3da5825dd4aa45b788e commit fb9e63701335b7383622e3da5825dd4aa45b788e Author: Tom Tromey <tom@tromey.com> Date: Sat Apr 30 12:51:17 2022 -0600 Remove unnecessary line from catch_exec_command_1 catch_exec_command_1 clears the new catchpoint's "exec_pathname" field, but this is already done by virtue of calling "new". Diff: --- gdb/break-catch-exec.c | 1 - 1 file changed, 1 deletion(-) diff --git a/gdb/break-catch-exec.c b/gdb/break-catch-exec.c index 00a0263ac0d..fbdc1c20e50 100644 --- a/gdb/break-catch-exec.c +++ b/gdb/break-catch-exec.c @@ -205,7 +205,6 @@ catch_exec_command_1 (const char *arg, int from_tty, std::unique_ptr<exec_catchpoint> c (new exec_catchpoint ()); init_catchpoint (c.get (), gdbarch, temp, cond_string); - c->exec_pathname.reset (); install_breakpoint (0, std::move (c), 1); }
reply other threads:[~2022-05-06 18:10 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=20220506181041.D3AF4395201B@sourceware.org \ --to=tromey@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).