git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bruce Korb <bruce.korb@gmail.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: GIT Development <git@vger.kernel.org>
Subject: Re: seg fault in "git format-patch"
Date: Sun, 31 May 2015 13:45:11 -0700	[thread overview]
Message-ID: <CAKRnqNJnaLioQPWYDmSiBfLCSMGdFR21bAEXRzdpkChDBf2wgw@mail.gmail.com> (raw)
In-Reply-To: <CAKRnqNKVfzt_qMqoxsjMpunUYDNYd8C0jACM69HxGhJHEeVY-Q@mail.gmail.com>

Oh, you can also clone the gnu-pw-mgr and likely get the same result:

$ cat .git/config
[core]
        repositoryformatversion = 0
        filemode = true
        bare = false
        logallrefupdates = true
[remote "origin"]
        fetch = +refs/heads/*:refs/remotes/origin/*
        url = ssh://git.sv.gnu.org/srv/git/gnu-pw-mgr.git
[branch "master"]
        remote = origin
        merge = refs/heads/master

On Sun, May 31, 2015 at 1:41 PM, Bruce Korb <bruce.korb@gmail.com> wrote:
> bt won't help much:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x000000000047e62f in ?? ()
> (gdb) bt
> #0  0x000000000047e62f in ?? ()
> #1  0x000000000047e6ba in ?? ()
> #2  0x000000000043cb9a in ?? ()
> #3  0x000000000043e9cc in ?? ()
> #4  0x000000000040647d in ?? ()
> #5  0x0000000000405863 in ?? ()
> #6  0x00007ffff6fc3be5 in __libc_start_main () from /lib64/libc.so.6
> #7  0x0000000000405cd5 in ?? ()
>
> $ git --version
> git version 1.8.4.5
> $ rpm -q -a|grep  '^git'
> git-email-1.8.4.5-3.8.4.x86_64
> gitg-0.2.7-3.1.4.x86_64
> git-cvs-1.8.4.5-3.8.4.x86_64
> git-svn-1.8.4.5-3.8.4.x86_64
> git-web-1.8.4.5-3.8.4.x86_64
> git-gui-1.8.4.5-3.8.4.x86_64
> gitg-lang-0.2.7-3.1.4.noarch
> git-1.8.4.5-3.8.4.x86_64
> git-core-1.8.4.5-3.8.4.x86_64
> gitk-1.8.4.5-3.8.4.x86_64
>
> $ head -n 300 /etc/*eleas*
> ==> /etc/SuSE-release <==
> openSUSE 13.1 (x86_64)
> VERSION = 13.1
> CODENAME = Bottle
> # /etc/SuSE-release is deprecated and will be removed in the future,
> use /etc/os-release instead
>
> ==> /etc/lsb-release <==
> LSB_VERSION="core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x86_64:core-3.2-x86_64:core-4.0-x86_64"
>
> ==> /etc/lsb-release.d <==
> head: error reading '/etc/lsb-release.d': Is a directory
>
> ==> /etc/os-release <==
> NAME=openSUSE
> VERSION="13.1 (Bottle)"
> VERSION_ID="13.1"
> PRETTY_NAME="openSUSE 13.1 (Bottle) (x86_64)"
> ID=opensuse
> ANSI_COLOR="0;32"
> CPE_NAME="cpe:/o:opensuse:opensuse:13.1"
> BUG_REPORT_URL="https://bugs.opensuse.org"
> HOME_URL="https://opensuse.org/"
> ID_LIKE="suse"
>
>
> On Sun, May 31, 2015 at 1:26 PM, Christian Couder
> <christian.couder@gmail.com> wrote:
>> 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.

  reply	other threads:[~2015-05-31 20:45 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
2015-05-31 20:41   ` Bruce Korb
2015-05-31 20:45     ` Bruce Korb [this message]
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=CAKRnqNJnaLioQPWYDmSiBfLCSMGdFR21bAEXRzdpkChDBf2wgw@mail.gmail.com \
    --to=bruce.korb@gmail.com \
    --cc=christian.couder@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).