Re: Bus error on Leopard with 64-bit program
Re: Bus error on Leopard with 64-bit program
- Subject: Re: Bus error on Leopard with 64-bit program
- From: bob <email@hidden>
- Date: Sat, 10 Nov 2007 13:56:19 -0500
The reason is because I had a very large repository that was failing
under 32-bit git and Linus Torvalds wanted to see if git would
process the repository under 64-bit. I am posting on the git mailing
list about my experiences compiling and running git under 64-bit on
Tiger and Leopard. Tiger did not supply 64-bit libraries to link
against so it is out unless I want to make my own and my experience
with Leopard is described below.
The first error seems to be:
Error Formulating Crash Report:
-[NSCFDictionary setObject:forKey:]: attempt to insert nil value
(key: VMUSignaturePath)
which is probably not within git. I googled VMUSignaturePath and
came up with nothing.
The crash report is very terse and doesn't really give much data
related to the actual SIGBUS which is what triggered the crash report
in the first place (my guess because I have never looked at a crash
report until now). (I have read a lot of OS/VS1, OS/MVS and CICS
dumps though!)
On Nov 10, 2007, at 1:06 PM, Bill Bumgarner wrote:
On Nov 10, 2007, at 9:48 AM, bob wrote:
I know that a bus error is not a problem for this list, but I
would like to confirm that I did things correctly when I compiled
the program that failed. It was git v1.5.3.5 which is an SCM. I
compiled and linked it with "-m64 -arch x86_64" which was
successful. When I ran it, it showed as 64-bit in Activity
Monitor before it crashed. Are the "-m64 -arch x86_64" all that I
needed? This is my first venture into 64-bit programs. So, I
just wanted to confirm that I did things correctly before I bother
Apple with the crashreport. Thanks in advance for your help.
Sounds about right. Unless GIT tickles a 64 bit specific bug in
Apple's frameworks/libraries, the crashreport isn't going to be
useful to Apple.
There might be any number of problems within the GIT source in
regards to 64 bit; assumptions about pointer size, etc...
The real question is why bother porting git to 64 bit?
Git is mostly I/O bound and certainly doesn't need to ever allocate
64 bits worth of memory (and, if it did, it'll page like heck on
all but systems with the necessary GBs of memory to keep the
working set resident).
If this is an educational exercise, great! But you'll likely find
that you'll learn more about porting to 64 bit if you start with a
slightly different project than git -- something graphics oriented
that could potentially work with a large chunk of memory.
b.bum
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden