From: Brian Moran <bmoran@onehub.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Bus Error- git merge
Date: Fri, 30 Jan 2009 10:15:44 -0800 [thread overview]
Message-ID: <C5A883D0.E243%bmoran@onehub.com> (raw)
I am getting a bus error on a git merge, including the more recent versions.
Following the instructions from a bug August, I got the latest sources,
compiled them up, and executed the merge in the debugger to repro. Here¹s
what I found:
gdb ../git-1.6.1.2/git-merge
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) set args -v v1-ftp-support
(gdb) run
Starting program: /Users/bmo/Documents/repo/git-1.6.1.2/git-merge -v
v1-ftp-support
Reading symbols for shared libraries +++++++. done
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x00000004
0x000863c3 in sha_eq (a=0x4 <Address 0x4 out of bounds>, b=0x7bf004 "<some
random chars>") at cache.h:575
575 return memcmp(sha1, sha2, 20);
(gdb) backtrace
#0 0x000863c3 in sha_eq (a=0x4 <Address 0x4 out of bounds>, b=0x7bf004
"<some random chars>") at cache.h:575
#1 0x00086dc6 in merge_trees (o=0xbfffedd4, head=0x7bf020, merge=0x7bf000,
common=0x0, result=0xbfffed28) at merge-recursive.c:1164
#2 0x00088960 in merge_recursive (o=0xbfffedd4, h1=0x4f4060, h2=0x4f4000,
ca=0x53cc20, result=0xbfffee2c) at merge-recursive.c:1294
#3 0x0003871c in try_merge_strategy (strategy=0xd28ce "recursive",
common=0x53a040, head_arg=0xc3508 "HEAD") at builtin-merge.c:586
#4 0x00039fef in cmd_merge (argc=1, argv=0xbffff860, prefix=0x0) at
builtin-merge.c:1131
#5 0x000025db in handle_internal_command (argc=3, argv=0xbffff860) at
git.c:243
#6 0x00002c48 in main (argc=3, argv=0xbffff860) at git.c:453
(gdb)
Any suggestions on how to proceed? I am available to gather more information
on this as I can reproduce at will.
Thanks,
Brian Moran
http://www.onehub.com
next reply other threads:[~2009-01-30 18:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 18:15 Brian Moran [this message]
2009-01-30 18:57 ` Bus Error- git merge Johannes Schindelin
2009-01-31 0:05 ` Brian Moran
2009-02-01 22:48 ` Johannes Schindelin
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=C5A883D0.E243%bmoran@onehub.com \
--to=bmoran@onehub.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).