From: "Shawn O. Pearce" <spearce@spearce.org>
To: git@vger.kernel.org
Subject: FLEX_ARRAY=1 causes SIGSEGV on SPARC
Date: Mon, 17 Dec 2007 20:01:26 -0500 [thread overview]
Message-ID: <20071218010126.GP14735@spearce.org> (raw)
So today I discovered latest master will cause a SIGSEGV on
Solaris/SPARC if FLEX_ARRAY is defined to the default value of 1.
The issue is the (old) compiler I'm using from Sun doesn't pass
the tests defined in 8e9739914972419baad820e76b44d9720ed885c2 (aka
"git-compat-util.h: auto-adjust to compiler support of FLEX_ARRAY
a bit better") so we fallback to #define FLEX_ARRAY 1.
Then git-pack-objects finds something unaligned and segfaults.
It always segfaults. During the deltification phase. Probably it
was working on deltifying loose objects; the set I fed it was about
100 most recent objects so they were probably all loose.
I'll try to track it down tomorrow. But the immediate workaround was
to just add '-DFLEX_ARRAY=/* empty */' to my CFLAGS and recompile
the world. This compiler accepts the empty FLEX_ARRAY macro but
I'm not sure what feature test(s) would be necessary to make Git
able to automatically set that, seeing as how the tests defined in
8e97 are perfectly reasonable and didn't pass.
Yea, yea, shame on me for not testing Git since Nov 20th on this
system... I should have caught the failure sooner. I'm buried in
non-Git work these days, but will try to come up with a reasonable
detection patch. Maybe someone will beat me to it. :-)
--
Shawn.
next reply other threads:[~2007-12-18 1:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 1:01 Shawn O. Pearce [this message]
2007-12-18 1:08 ` FLEX_ARRAY=1 causes SIGSEGV on SPARC Junio C Hamano
2007-12-18 1:32 ` [PATCH] diff-delta.c: make FLEX_ARRAY=1 work David Kastrup
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=20071218010126.GP14735@spearce.org \
--to=spearce@spearce.org \
--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).