public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Enze Li <lienze@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] gdbserver: remove unused for loop Date: Sat, 24 Sep 2022 04:01:02 +0000 (GMT) [thread overview] Message-ID: <20220924040102.952A33858D28@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b7098e650c9f1ced654c939bebd4b70e7d028132 commit b7098e650c9f1ced654c939bebd4b70e7d028132 Author: Enze Li <enze.li@hotmail.com> Date: Thu Sep 22 21:17:31 2022 +0800 gdbserver: remove unused for loop In this commit, commit cf6c1e710ee162a5adb0ae47acb731f2bfecc956 Date: Mon Jul 11 20:53:48 2022 +0800 gdbserver: remove unused variable I removed an unused variable in handle_v_run. Pedro then pointed out that the for loop after it was also unused. After a period of smoke testing, no exceptions were found. Tested on x86_64-linux. Diff: --- gdbserver/server.cc | 3 --- 1 file changed, 3 deletions(-) diff --git a/gdbserver/server.cc b/gdbserver/server.cc index c619206d5d2..366a843ea89 100644 --- a/gdbserver/server.cc +++ b/gdbserver/server.cc @@ -2984,9 +2984,6 @@ handle_v_run (char *own_buf) char *new_program_name = NULL; int i; - for (p = own_buf + strlen ("vRun;"); p && *p; p = strchr (p, ';')) - p++; - for (i = 0, p = own_buf + strlen ("vRun;"); *p; p = next_p, ++i) { next_p = strchr (p, ';');
reply other threads:[~2022-09-24 4:01 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=20220924040102.952A33858D28@sourceware.org \ --to=lienze@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).