On Feb 18, 2008, at 9:36 AM, Dane Jensen wrote:
Hi all-
Somehow I've managed to create a repository that causes git status
to segfault. To be honest, I'm not entirely sure how just yet. This
comes after a weekend of splitting a repository into two separate
repositories, filtering out a directory from one, and then creating
grafts in those repositories to skip commits that now change nothing.
I have the same problem, also on OS X.
Vienna:Project pieter$ git --version
git version 1.5.4.2.263.g5729
which is 'next' + 2 patches
Vienna:Project pieter$ gdb --args git status
GNU gdb 6.3.50-20050815 (Apple version gdb-768) (Tue Oct 2 04:07:49
UTC 2007)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and
you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "i386-apple-darwin"...Reading symbols for
shared libraries ........ done
(gdb) r
Starting program: /opt/pieter/bin/git status
Reading symbols for shared libraries +++++++. done
# On branch master
# Changed but not updated:
# (use "git add <file>..." to update what will be committed)
#
# modified: Data/Metadata/redirects.xml
# modified: protege/ontologie.owl
# modified: protege/ontologie.pprj
# modified: protege/ontologie.repository
# modified: protege/swirl_data.owl
# modified: test-po2s.db
# modified: test-so2p.db
# modified: test-sp2o.db
#
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x004a2010
index_name_exists (istate=0xeba80, name=0xbfffdc27 "Data/Cache/
Template/Peter_II_of_Yugoslavia.html", namelen=47) at read-cache.c:101
101 if (!(ce->ce_flags & CE_UNHASHED)) {
(gdb) print *ce
Cannot access memory at address 0x4a1fec
This happens in at least one repository, most others are just fine.
- Pieter
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
