From: Jonathan Nieder <jrnieder@gmail.com>
To: Ralf Thielow <ralf.thielow@gmail.com>
Cc: git <git@vger.kernel.org>,
"Andrés G. Aragoneses" <knocte@gmail.com>,
"Duy Nguyen" <pclouds@gmail.com>
Subject: Re: Segfault when fetching from current git.git on GitHub
Date: Tue, 3 Dec 2013 11:20:18 -0800 [thread overview]
Message-ID: <20131203192018.GD29959@google.com> (raw)
In-Reply-To: <CAN0XMOKPWm1CzS3289SHpH=N0osFszuvnK6e9BVxwtQe3b2YJg@mail.gmail.com>
Hi,
Ralf Thielow wrote:
> I've fetched from the current git.git on GitHub minutes ago and got a
> segfault. I could reproduce it with the Git version of the current "next" branch
> (1.8.5.392.gf545f4d) with the steps below. The segfault does not appear with
> version 1.8.5.
Yep, I can reproduce this.
(gdb) bt
#0 next_quote_pos (s=0x0, maxlen=-1) at quote.c:168
#1 0x00000000004ca2bb in quote_c_style_counted (name=0x0, maxlen=-1, sb=0x7fffffffe290, fp=0x0, no_dq=0) at quote.c:215
#2 0x00000000004fd4c0 in set_helper_option (transport=<optimized out>, name=0x525f89 "depth", value=0x0) at transport-helper.c:307
#3 0x00000000004fb57f in transport_set_option (transport=0x7d5740, name=<optimized out>, value=0x0) at transport.c:1004
#4 0x000000000042de10 in backfill_tags (ref_map=0x806a50, transport=0x7d5740) at builtin/fetch.c:791
It's fallout from 0f284b11 (transport: catch non positive --depth
option value, 2013-11-26).
prev parent reply other threads:[~2013-12-03 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 18:56 Segfault when fetching from current git.git on GitHub Ralf Thielow
2013-12-03 19:20 ` Jonathan Nieder [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=20131203192018.GD29959@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=knocte@gmail.com \
--cc=pclouds@gmail.com \
--cc=ralf.thielow@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.
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.