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 0x004ca2bb in quote_c_style_counted (name=0x0, maxlen=-1,
sb=0x7fffe290, fp=0x0, no_dq=0) at quote.c:215
#2 0x004fd4c0 in set_helper_option (transport=,
name=0x525f89 "depth", value=0x0) at transport-helper.c:307
#3 0x004fb57f in transport_set_option (transport=0x7d5740,
name=, value=0x0) at transport.c:1004
#4 0x0042de10 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).
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html