From: Brian Harring <ferringb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] get_indexed_object can return NULL if nothing is in that slot; check for it
Date: Wed, 24 Aug 2011 13:40:21 -0700 [thread overview]
Message-ID: <20110824204021.GA28157@beast> (raw)
In-Reply-To: <7vmxeypudw.fsf@alter.siamese.dyndns.org>
On Wed, Aug 24, 2011 at 10:54:51AM -0700, Junio C Hamano wrote:
> Thanks for a fix.
>
> It is both interesting and disturbing to see that these small mistakes are
> discovered a week after the topics hit 'master', even though it has been
> cooking in 'next' for a week before that happened (in the case of this
> topic, it also hit 'maint' yesterday).
I'll admit I'm slightly surprised it slipped past for initial
development- that said, you have to explicitly trigger the race to
trigger the segfault. And that's not easy w/out building out a
custom setup- even w/ that setup, you need to go digging in server
logs to realize the previous serverside failure just converted to a
segfault. Clientside, it hung just the same.
Bit nonobvious. Plus, shit happens. ;)
Either way, I was poking at the source trying to figure out how to get
some unittests for an end to end testing of the http/smartserv; that
said I was having a helluva time finding a way to do it without
bundling a stub of a webserver. Suggestions would be welcome on that
one.
~brian
next prev parent reply other threads:[~2011-08-24 20:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 5:47 [PATCH] get_indexed_object can return NULL if nothing is in that slot; check for it Brian Harring
2011-08-24 17:54 ` Junio C Hamano
2011-08-24 20:40 ` Brian Harring [this message]
2011-08-24 21:10 ` Junio C Hamano
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=20110824204021.GA28157@beast \
--to=ferringb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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).