From: Raymond Jennings <shentino@gmail.com>
To: git@vger.kernel.org
Subject: [BUG] Segfault in "git submodule"
Date: Sat, 29 Sep 2018 08:22:50 -0700 [thread overview]
Message-ID: <CAGDaZ_oBpLxD0cutrsNsFBEtH+-Fn2eT40gDsnGZhhU0qm2Ofw@mail.gmail.com> (raw)
[New LWP 19644]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `git submodule--helper status'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 refs_read_raw_ref (type=<optimized out>, referent=<optimized out>,
oid=<optimized out>, refname=<optimized out>, ref_store=<optimized
out>) at refs.c:1451
1451 return ref_store->be->read_raw_ref(ref_store, refname, oid,
referent, type);
#0 refs_read_raw_ref (type=<optimized out>, referent=<optimized out>,
oid=<optimized out>, refname=<optimized out>, ref_store=<optimized
out>) at refs.c:1451
#1 refs_resolve_ref_unsafe (refs=0x0,
refname=refname@entry=0x55e863062253 "HEAD",
resolve_flags=resolve_flags@entry=1, oid=oid@entry=0x7ffdc834b1c0,
flags=flags@entry=0x7ffdc834b1bc) at refs.c:1493
#2 0x000055e862fcad5c in refs_read_ref_full (flags=0x7ffdc834b1bc,
oid=0x7ffdc834b1c0, resolve_flags=1, refname=0x55e863062253 "HEAD",
refs=<optimized out>) at refs.c:224
#3 refs_head_ref (refs=<optimized out>, fn=fn@entry=0x55e862f25fb0
<handle_submodule_head_ref>, cb_data=cb_data@entry=0x7ffdc834b300) at
refs.c:1314
#4 0x000055e862f292a2 in status_submodule (flags=0, prefix=<optimized
out>, ce_flags=0, ce_oid=0x55e86468d4d4, path=0x55e86468d4e8
"lpc-doc") at builtin/submodule--helper.c:624
#5 status_submodule_cb (cb_data=0x7ffdc834b240,
list_item=0x55e86468d490) at builtin/submodule--helper.c:665
#6 for_each_listed_submodule (cb_data=<optimized out>, fn=<optimized
out>, list=<optimized out>) at builtin/submodule--helper.c:404
#7 module_status (argc=<optimized out>, argv=<optimized out>,
prefix=<optimized out>) at builtin/submodule--helper.c:698
#8 0x000055e862eaec95 in run_builtin (argv=<optimized out>,
argc=<optimized out>, p=<optimized out>) at git.c:346
#9 handle_builtin (argc=<optimized out>, argv=<optimized out>) at git.c:554
#10 0x000055e862eaf985 in run_argv (argv=0x7ffdc834be20,
argcp=0x7ffdc834be2c) at git.c:606
#11 cmd_main (argc=<optimized out>, argv=<optimized out>) at git.c:683
#12 0x000055e862eae96a in main (argc=3, argv=0x7ffdc834c078) at common-main.c:43
next reply other threads:[~2018-09-29 15:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-29 15:22 Raymond Jennings [this message]
2018-09-29 15:29 ` [BUG] Segfault in "git submodule" Ævar Arnfjörð Bjarmason
2018-09-29 15:33 ` Duy Nguyen
2018-09-29 16:43 ` Raymond Jennings
2018-10-01 19:19 ` Stefan Beller
2018-10-01 21:31 ` Raymond Jennings
2018-10-02 4:10 ` Raymond Jennings
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGDaZ_oBpLxD0cutrsNsFBEtH+-Fn2eT40gDsnGZhhU0qm2Ofw@mail.gmail.com \
--to=shentino@gmail.com \
--cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).