From: Karsten Blees <karsten.blees@gmail.com>
To: Git List <git@vger.kernel.org>,
msysGit <msysgit@googlegroups.com>, Jeff King <peff@peff.net>
Subject: [PATCH v5 04/11] trace: factor out printing to the trace file
Date: Wed, 11 Jun 2014 09:58:25 +0200 [thread overview]
Message-ID: <53980C21.5080203@gmail.com> (raw)
In-Reply-To: <53980B83.9050409@gmail.com>
Opening and writing to the trace file is currently duplicated in
trace_strbuf() and trace_argv_printf(). Factor out this logic to prepare
for adding timestamp and file:line to trace output.
In case of trace_argv_printf(), this adds an additional trace_want() check
to prevent unnecessary string formatting.
Signed-off-by: Karsten Blees <blees@dcon.de>
---
trace.c | 37 +++++++++++++++++++------------------
1 file changed, 19 insertions(+), 18 deletions(-)
diff --git a/trace.c b/trace.c
index 3e31558..b7ca51b 100644
--- a/trace.c
+++ b/trace.c
@@ -62,6 +62,21 @@ static int get_trace_fd(const char *key, int *need_close)
static const char err_msg[] = "Could not trace into fd given by "
"GIT_TRACE environment variable";
+/* Print 'buf' verbatim to trace file designated by env var 'key' */
+static void do_trace_print(const char *key, const struct strbuf *buf)
+{
+ int fd, need_close = 0;
+
+ fd = get_trace_fd(key, &need_close);
+ if (!fd)
+ return;
+
+ write_or_whine_pipe(fd, buf->buf, buf->len, err_msg);
+
+ if (need_close)
+ close(fd);
+}
+
static void trace_vprintf(const char *key, const char *format, va_list ap)
{
struct strbuf buf = STRBUF_INIT;
@@ -71,7 +86,7 @@ static void trace_vprintf(const char *key, const char *format, va_list ap)
set_try_to_free_routine(NULL); /* is never reset */
strbuf_vaddf(&buf, format, ap);
- trace_strbuf(key, &buf);
+ do_trace_print(key, &buf);
strbuf_release(&buf);
}
@@ -93,26 +108,15 @@ void trace_printf(const char *format, ...)
void trace_strbuf(const char *key, const struct strbuf *buf)
{
- int fd, need_close = 0;
-
- fd = get_trace_fd(key, &need_close);
- if (!fd)
- return;
-
- write_or_whine_pipe(fd, buf->buf, buf->len, err_msg);
-
- if (need_close)
- close(fd);
+ do_trace_print(key, buf);
}
void trace_argv_printf(const char **argv, const char *format, ...)
{
struct strbuf buf = STRBUF_INIT;
va_list ap;
- int fd, need_close = 0;
- fd = get_trace_fd("GIT_TRACE", &need_close);
- if (!fd)
+ if (!trace_want("GIT_TRACE"))
return;
set_try_to_free_routine(NULL); /* is never reset */
@@ -122,11 +126,8 @@ void trace_argv_printf(const char **argv, const char *format, ...)
sq_quote_argv(&buf, argv, 0);
strbuf_addch(&buf, '\n');
- write_or_whine_pipe(fd, buf.buf, buf.len, err_msg);
+ do_trace_print("GIT_TRACE", &buf);
strbuf_release(&buf);
-
- if (need_close)
- close(fd);
}
static const char *quote_crnl(const char *path)
--
1.9.2.msysgit.0.501.gaeecf09
--
--
*** Please reply-to-all at all times ***
*** (do not pretend to know who is subscribed and who is not) ***
*** Please avoid top-posting. ***
The msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free.
You received this message because you are subscribed to the Google
Groups "msysGit" group.
To post to this group, send email to msysgit@googlegroups.com
To unsubscribe from this group, send email to
msysgit+unsubscribe@googlegroups.com
For more options, and view previous threads, visit this group at
http://groups.google.com/group/msysgit?hl=en_US?hl=en
---
You received this message because you are subscribed to the Google Groups "msysGit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to msysgit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2014-06-11 7:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 7:55 [PATCH v5 00/11] add performance tracing facility Karsten Blees
2014-06-11 7:56 ` [PATCH v5 01/11] trace: move trace declarations from cache.h to new trace.h Karsten Blees
2014-06-11 7:57 ` [PATCH v5 02/11] trace: consistently name the format parameter Karsten Blees
2014-06-11 7:57 ` [PATCH v5 03/11] trace: remove redundant printf format attribute Karsten Blees
2014-06-11 7:58 ` Karsten Blees [this message]
2014-06-11 7:59 ` [PATCH v5 05/11] trace: add infrastructure to augment trace output with additional info Karsten Blees
2014-06-11 7:59 ` [PATCH v5 06/11] trace: add current timestamp to all trace output Karsten Blees
2014-06-11 8:00 ` [PATCH v5 07/11] trace: move code around, in preparation to file:line output Karsten Blees
2014-06-11 8:00 ` [PATCH v5 08/11] trace: add 'file:line' to all trace output Karsten Blees
2014-06-11 8:01 ` [PATCH v5 09/11] trace: add high resolution timer function to debug performance issues Karsten Blees
2014-06-11 8:12 ` Karsten Blees
2014-06-17 16:44 ` Junio C Hamano
2014-06-18 15:14 ` Karsten Blees
2014-06-11 8:01 ` [PATCH v5 10/11] trace: add trace_performance facility " Karsten Blees
2014-06-17 17:11 ` Junio C Hamano
2014-06-18 15:14 ` Karsten Blees
2014-06-18 17:28 ` Junio C Hamano
2014-06-11 8:02 ` [PATCH v5 11/11] git: add performance tracing for git's main() function to debug scripts Karsten Blees
2014-06-12 18:30 ` [PATCH v5 00/11] add performance tracing facility Junio C Hamano
2014-06-18 15:14 ` Karsten Blees
2014-06-25 14:28 ` Duy Nguyen
2014-06-25 14:49 ` Karsten Blees
2014-06-26 1:11 ` Duy Nguyen
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=53980C21.5080203@gmail.com \
--to=karsten.blees@gmail.com \
--cc=git@vger.kernel.org \
--cc=msysgit@googlegroups.com \
--cc=peff@peff.net \
/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).