From: Christian Couder <christian.couder@gmail.com>
To: Bruce Korb <bruce.korb@gmail.com>
Cc: GIT Development <git@vger.kernel.org>
Subject: Re: seg fault in "git format-patch"
Date: Sun, 31 May 2015 22:26:15 +0200 [thread overview]
Message-ID: <CAP8UFD0Pi3_hF0+S3AXktD5NkBL_Q1mU_oN4fULyZemDEUr8Jg@mail.gmail.com> (raw)
In-Reply-To: <556B5D4C.4030406@gmail.com>
On Sun, May 31, 2015 at 9:13 PM, Bruce Korb <bruce.korb@gmail.com> wrote:
> $ git format-patch -o patches --ignore-if-in-upstream
> 14949fa8f39d29e44b43f4332ffaf35f11546502..2de9eef391259dfc8748dbaf76a5d55427f37b0d
> Segmentation fault
> /u/gnu/proj/gnu-pw-mgr
> $ git format-patch -o patches
> 14949fa8f39d29e44b43f4332ffaf35f11546502..2de9eef391259dfc8748dbaf76a5d55427f37b0d
> patches/0001-remove-dead-code.patch
> patches/0002-dead-code-removal.patch
> patches/0003-add-sort-pw-cfg-program.patch
> patches/0004-add-doc-for-sort-pw-cfg.patch
> patches/0005-clean-up-doc-makefile.patch
> patches/0006-clean-up-doc-makefile.patch
> patches/0007-happy-2015-and-add-delete-option.patch
> patches/0008-fix-doc-Makefile.am.patch
> patches/0009-re-fix-copyright.patch
> patches/0010-finish-debugging-remove_pwid.patch
> patches/0011-only-update-file-if-something-was-removed.patch
> patches/0012-update-NEWS.patch
> patches/0013-bootstrap-cleanup.patch
Could you tell us which git version you are using? You can use "git --version".
The operating system you are using could also be useful.
And maybe you could also run git under gdb and give us the output of
the "bt" (backtrace) gdb command when it crashes?
Thanks,
Christian.
next prev parent reply other threads:[~2015-05-31 20:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-31 19:13 seg fault in "git format-patch" Bruce Korb
2015-05-31 20:26 ` Christian Couder [this message]
2015-05-31 20:41 ` Bruce Korb
2015-05-31 20:45 ` Bruce Korb
2015-05-31 23:14 ` Christian Couder
2015-05-31 23:53 ` Christian Couder
2015-06-01 0:01 ` Christian Couder
2015-06-01 1:03 ` [PATCH] format-patch: dereference tags with --ignore-if-in-upstream brian m. carlson
2015-06-01 10:20 ` Jeff King
2015-06-01 11:22 ` brian m. carlson
2015-06-01 11:47 ` Jeff King
2015-06-01 14:56 ` Junio C Hamano
2015-06-01 17:44 ` Junio C Hamano
2015-06-01 17:47 ` Jeff King
2015-06-01 20:35 ` Junio C Hamano
2015-06-01 22:34 ` brian m. carlson
2015-06-01 22:46 ` Junio C Hamano
2015-06-01 17:58 ` Junio C Hamano
2015-06-01 13:44 ` seg fault in "git format-patch" Christian Couder
2015-06-01 14:17 ` Christian Couder
2015-06-01 14:47 ` Bruce Korb
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=CAP8UFD0Pi3_hF0+S3AXktD5NkBL_Q1mU_oN4fULyZemDEUr8Jg@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=bruce.korb@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.
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).