From: Derrick Stolee <email@example.com> To: Sathyajith Bhat <firstname.lastname@example.org>, email@example.com Subject: Re: Segfault in git when using git logs Date: Tue, 3 Nov 2020 13:46:12 -0500 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <CAMsWJsyPVQWV++gc2YJriEOEWBELa_xj2G0NWFMSgNYt47swiQ@mail.gmail.com> On 11/2/2020 8:59 AM, Sathyajith Bhat wrote: > Anything else you want to add: Hi Sathyajith, It seems like others have some good approaches to handling this segfault and making sure we find the right balance between supporting existing behavior and helping callers who might be using this command incorrectly. > Note that I am not calling the git log commands directly, my editor VS > Code was repeatedly crashing and I searched in syslog and found this > error. I started filling out an issue on the VS Code GitHub repo so they could perhaps fix their usage of "git log" in this case. However, I started searching their code for where they might be executing the command, and I didn't find anything! Is it possible that you have an extension that enables Git history commands like this? The VS Code bug report issue template  has this bit of advice to find out if an extension is at fault: > <!-- Launch with `code --disable-extensions` to check. --> > Does this issue occur when all extensions are disabled?: Yes/No  https://github.com/microsoft/vscode/issues/new?template=bug_report.md Could you re-launch your editor with "--disable-extensions" to see if this is reproduced? Also, which extensions do you have installed that might be adding Git command calls? We might need to find the extension authors instead of the core editor team. Thanks, -Stolee
next prev parent reply other threads:[~2020-11-03 18:46 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-02 13:59 Sathyajith Bhat 2020-11-02 14:43 ` Jeff King 2020-11-02 18:31 ` Junio C Hamano 2020-11-03 10:15 ` SZEDER Gábor 2020-11-03 11:21 ` Christian Couder 2020-11-03 16:10 ` Elijah Newren 2020-11-03 18:21 ` Jeff King 2020-11-03 18:34 ` Junio C Hamano 2020-11-03 18:57 ` Jeff King 2020-11-03 20:21 ` Junio C Hamano 2020-11-04 13:31 ` Jeff King 2020-11-04 16:26 ` Junio C Hamano 2020-11-04 17:54 ` Re*: " Junio C Hamano 2020-11-04 19:41 ` Jeff King 2020-11-04 20:16 ` Junio C Hamano 2020-11-04 20:35 ` [PATCH] log: diagnose -L used with pathspec as an error Junio C Hamano 2020-11-04 21:03 ` Jeff King 2020-11-03 18:46 ` Derrick Stolee [this message] 2020-11-03 18:55 ` Segfault in git when using git logs Sathyajith Bhat 2020-11-03 19:23 ` Jeff King 2020-11-03 20:07 ` Derrick Stolee 2020-11-03 21:04 ` Derrick Stolee 2020-11-04 15:49 ` Sathyajith Bhat
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Segfault in git when using git logs' \ /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
Code repositories for project(s) associated with this 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).