git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "René Scharfe" <l.s.r@web.de>
To: Duy Nguyen <pclouds@gmail.com>, Jeff King <peff@peff.net>
Cc: Christian Couder <christian.couder@gmail.com>,
	Thomas Gummerer <t.gummerer@gmail.com>, git <git@vger.kernel.org>,
	Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] cache-tree: reject entries with null sha1
Date: Mon, 1 May 2017 13:55:03 +0200	[thread overview]
Message-ID: <8754b32d-9eec-973d-a225-175085fc7e82@web.de> (raw)
In-Reply-To: <12c3312c-30a1-2cb1-8f05-63bb663bd0a0@web.de>

Am 01.05.2017 um 13:23 schrieb René Scharfe:
> But I can't get Valgrind to report overlapping (nicely explained in
> http://valgrind.org/docs/manual/mc-manual.html#mc-manual.overlap, by
> the way), not for t7009 and not for the short test program at the
> bottom.  Do you set flags in GIT_VALGRIND_OPTIONS or use a special
> version of Valgrind?  I use valgrind-3.12.0.SVN from Debian testing.
> 
> Thanks,
> René
> 
> 
> /* Compile with -fno-builtin. */
> #include <string.h>
> int main(void) {int i = 1; memcpy(&i, &i, sizeof(i)); return i;}

Actually I can, on Debian stable x86 (Valgrind-3.10.0).  Not sure
whether it's the older version of Valgrind or the 32-bitness, but
it gives me a way to reproduce, so nevermind.

René

  reply	other threads:[~2017-05-01 11:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-21 18:46 [PATCH] cache-tree: reject entries with null sha1 Jeff King
2017-04-24 10:39 ` Duy Nguyen
2017-04-24 11:13   ` Jeff King
2017-05-01 11:23   ` René Scharfe
2017-05-01 11:55     ` René Scharfe [this message]
2017-05-01 19:22     ` Jeff King
2017-05-01 21:00       ` René Scharfe
2017-05-01 21:26         ` Jeff King
2017-05-03  9:46       ` Duy Nguyen
2017-05-03 19:48         ` René Scharfe

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8754b32d-9eec-973d-a225-175085fc7e82@web.de \
    --to=l.s.r@web.de \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=pclouds@gmail.com \
    --cc=peff@peff.net \
    --cc=t.gummerer@gmail.com \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).