From: Elijah Newren <newren@gmail.com>
To: git@vger.kernel.org
Cc: Elijah Newren <newren@gmail.com>
Subject: [PATCH] Make running git under other debugger-like programs easy
Date: Thu, 5 Apr 2018 10:49:35 -0700 [thread overview]
Message-ID: <20180405174935.598-1-newren@gmail.com> (raw)
This allows us to run git, when using the script from bin-wrappers, under
other programs. A few examples:
GIT_WRAPPER=nemiver git $ARGS
GIT_WRAPPER="valgrind --tool=memcheck --track-origins=yes" git $ARGS
Yes, we already have GIT_TEST_GDB (which could potentially be replaced
with GIT_WRAPPER="gdb --args"), and a bunch of options for running
a testcase or multiple testcases under valgrind, but I find the extra
flexibility useful.
Signed-off-by: Elijah Newren <newren@gmail.com>
---
wrap-for-bin.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/wrap-for-bin.sh b/wrap-for-bin.sh
index 5842408817..1b34d44193 100644
--- a/wrap-for-bin.sh
+++ b/wrap-for-bin.sh
@@ -25,5 +25,5 @@ then
unset GIT_TEST_GDB
exec gdb --args "${GIT_EXEC_PATH}/@@PROG@@" "$@"
else
- exec "${GIT_EXEC_PATH}/@@PROG@@" "$@"
+ exec ${GIT_WRAPPER} "${GIT_EXEC_PATH}/@@PROG@@" "$@"
fi
--
2.17.0.7.g0b50f94d69
next reply other threads:[~2018-04-05 17:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 17:49 Elijah Newren [this message]
2018-04-05 19:57 ` [PATCH] Make running git under other debugger-like programs easy Johannes Schindelin
2018-04-05 21:16 ` Elijah Newren
2018-04-06 10:38 ` Johannes Schindelin
2018-04-06 22:36 ` Elijah Newren
2018-04-09 18:51 ` [PATCH v2] " Elijah Newren
2018-04-09 21:19 ` Johannes Schindelin
2018-04-10 0:48 ` Elijah Newren
2018-04-10 8:26 ` Johannes Schindelin
2018-04-24 23:46 ` [PATCH v3] " Elijah Newren
2018-04-25 7:25 ` Johannes Schindelin
2018-04-26 1:56 ` Junio C Hamano
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=20180405174935.598-1-newren@gmail.com \
--to=newren@gmail.com \
--cc=git@vger.kernel.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 NNTP newsgroup(s).