All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: David Turner <dturner@twopensource.com>
Cc: git@vger.kernel.org, David Turner <dturner@twitter.com>
Subject: Re: [PATCH] refs: Fix valgrind suppression file
Date: Mon, 07 Jul 2014 11:20:41 -0700	[thread overview]
Message-ID: <xmqqy4w5c9om.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1404505441-1853-1-git-send-email-dturner@twitter.com> (David Turner's message of "Fri, 4 Jul 2014 13:24:01 -0700")

David Turner <dturner@twopensource.com> writes:

> Add all of the ways in which check_refname_format violates valgrind's
> expectations to the valgrind suppression file; remove an assumption about
> the call chain of check_refname_format from same.
>
> Signed-off-by: David Turner <dturner@twitter.com>
> ---
>  t/valgrind/default.supp | 15 +++++++++++----
>  1 file changed, 11 insertions(+), 4 deletions(-)

I'll queue, but it makes me feel more and more disgusted with that
SSE patch, to be honest.

>
> diff --git a/t/valgrind/default.supp b/t/valgrind/default.supp
> index 332ab1a..9d51c92 100644
> --- a/t/valgrind/default.supp
> +++ b/t/valgrind/default.supp
> @@ -50,10 +50,17 @@
>  	fun:copy_ref
>  }
>  {
> -	ignore-sse-check_refname_format
> +	ignore-sse-check_refname_format-addr
>  	Memcheck:Addr8
>  	fun:check_refname_format
> -	fun:cmd_check_ref_format
> -	fun:handle_builtin
> -	fun:main
> +}
> +{
> +	ignore-sse-check_refname_format-cond
> +	Memcheck:Cond
> +	fun:check_refname_format
> +}
> +{
> +	ignore-sse-check_refname_format-value
> +	Memcheck:Value8
> +	fun:check_refname_format
>  }

      reply	other threads:[~2014-07-07 18:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-04 20:24 [PATCH] refs: Fix valgrind suppression file David Turner
2014-07-07 18:20 ` Junio C Hamano [this message]

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=xmqqy4w5c9om.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=dturner@twitter.com \
    --cc=dturner@twopensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.