All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: jongman.heo@samsung.com, Jonathan Nieder <jrnieder@gmail.com>,
	Thomas Rast <trast@student.ethz.ch>, git <git@vger.kernel.org>,
	Antoine Pelisse <apelisse@gmail.com>
Subject: Re: Segmentation fault with latest git (070c57df)
Date: Mon, 04 Feb 2013 01:16:08 -0800	[thread overview]
Message-ID: <7vsj5c4exz.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20130204083701.GA30835@sigill.intra.peff.net> (Jeff King's message of "Mon, 4 Feb 2013 03:37:01 -0500")

Jeff King <peff@peff.net> writes:

> Do we want to do anything with the other dependency hole I found here:
>
>   http://article.gmane.org/gmane.comp.version-control.git/215211
>
> It's definitely a potential problem, but I don't think we have any
> reports of it happening in practice, so it might not be worth worrying
> about. Doing a clean version of the fix here:
>
>   http://article.gmane.org/gmane.comp.version-control.git/215212
>
> would probably involve reorganizing our .depend directory structure,
> unless somebody can cook up some clever use of make's patsubst.

As I understand how the current set-up works:

 * Initially, we do not have foo.o but foo.c.  We automatically
   build foo.o because it depends on foo.c via the "%.o : %.c" rule,
   and as a side effect, we also build .depend/foo.o.d file;

 * Then, if any real dependency used to build the existing foo.o
   that is recorded in .depend/foo.o.d file changes, foo.o gets
   rebuilt, which would update .depend/foo.o.d again for the next
   invocation.

The case where you lose .depend/foo.o.d is a special case of getting
a wrong information in .depend/foo.o.d, which may happen by using a
broken compiler during the initial build, or going over quota and
getting .depend/foo.o.d truncated, or by other breakages.  The user
may have done "rm -rf .depend" to lose it, or the user may have done
something like this to munge it:

	find -name '.git' -type d -prune -o -print0 |
        xargs -0 sed -i -e 's/foo/bar/g'

forgetting that just like .git, .depend is precious and should not
be touched.

I think this really boils down to where we draw the "this is good
enough" line.  I am not sure if losing the file as in $gmane/215211
is common enough to be special cased to buy us much, while leaving
other ".depend/foo.o.d was updated to contain a wrong info" cases
still broken.

And of course the case where .depend/foo.o.d is munged by mistake
cannot be solved without recompiling everything all the time, so...

  reply	other threads:[~2013-02-04  9:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31  1:35 Segmentation fault with latest git (070c57df) Jongman Heo
2013-01-31  6:49 ` Jeff King
2013-01-31  7:02   ` Antoine Pelisse
2013-01-31  7:35     ` Jeff King
2013-02-04  6:58 ` Jongman Heo
2013-02-04  7:13   ` Junio C Hamano
2013-02-04  8:37     ` Jeff King
2013-02-04  9:16       ` Junio C Hamano [this message]
2013-02-04  9:29         ` Junio C Hamano
2013-02-04  9:45           ` Jeff King
2013-02-04  9:38         ` Jeff King
2013-02-04 16:46           ` Junio C Hamano
2013-02-04 18:34             ` Jonathan Nieder
2013-05-15  3:14               ` sam
2013-05-15  3:22                 ` sam
2013-05-16 13:12                 ` Ramkumar Ramachandra
2013-05-16 13:21                   ` Ramkumar Ramachandra
  -- strict thread matches above, loose matches on Subject: below --
2013-01-31  7:27 Jongman Heo
2013-01-31  7:55 ` Jeff King
2013-01-31  8:42   ` Thomas Rast
2013-01-31  8:54     ` Jeff King
2013-02-01  1:31 허종만
2013-02-01  1:40 ` Junio C Hamano
2013-02-01  6:36   ` Jeff King
2013-02-01  7:06     ` Jeff King
2013-02-01  7:09     ` Jeff King
2013-02-04  2:18 Re: Re: Re: " Jongman Heo
2013-02-04  3:40 ` Jonathan Nieder

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=7vsj5c4exz.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=apelisse@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jongman.heo@samsung.com \
    --cc=jrnieder@gmail.com \
    --cc=peff@peff.net \
    --cc=trast@student.ethz.ch \
    /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.