From: Nick Edelen <sirnot@gmail.com>
To: Nicolas Pitre <nico@cam.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Sam Vilain <sam@vilain.net>,
Michael J Gruber <git@drmicha.warpmail.net>,
Jeff King <peff@peff.net>,
"Shawn O. Pearce" <spearce@spearce.org>,
Andreas Ericsson <exon@op5.se>,
Christian Couder <christian@couder.net>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH 6/6 (v4)] support for path name caching in rev-cache
Date: Tue, 18 Aug 2009 13:31:49 +0200 [thread overview]
Message-ID: <c77435a80908180431k2f91e1ffye25aa8895908ddb7@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0908172235360.6044@xanadu.home>
AARGH scheissgepoops I'm so sorry :-(
> BOOM! :-( And now half of the git commands are just as helpful with
> segmentation faults, including 'git log'.
>
> Here's a backtrace from gdb:
I swear I must've been on drugs or something b/c I managed removed the
PROT_WRITE access permission from mmap :-/ cygwin didn't seem to
notice either. And there's also your explanation of my idiotic
directory permissions choice.
You're also right about the command output; I've added a bit in the
docs explaining the output of each command.
I'll reply to *these* posts with everything fixed. Then after that
hopefully I can just make patches for the patchset (yo dawg) and save
everyone a lot of bandwidth.
- Nick
next prev parent reply other threads:[~2009-08-18 11:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 12:31 [PATCH 6/6 (v4)] support for path name caching in rev-cache Nick Edelen
2009-08-18 3:24 ` Nicolas Pitre
2009-08-18 11:31 ` Nick Edelen [this message]
2009-08-19 3:52 ` Nicolas Pitre
2009-08-20 12:43 ` Nick Edelen
2009-08-20 23:22 ` Nick Edelen
2009-08-21 0:05 ` Nicolas Pitre
2009-08-18 11:54 ` Johannes Schindelin
2009-08-18 11:51 ` Nick Edelen
2009-08-21 4:48 ` Nick Edelen
2009-09-07 14:11 ` Nick Edelen
2009-10-02 22:12 ` Nick Edelen
2009-10-19 20:31 ` Nick Edelen
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=c77435a80908180431k2f91e1ffye25aa8895908ddb7@mail.gmail.com \
--to=sirnot@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=christian@couder.net \
--cc=exon@op5.se \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nico@cam.org \
--cc=peff@peff.net \
--cc=sam@vilain.net \
--cc=spearce@spearce.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).