From: Aidan Van Dyk <aidan@highrise.ca>
To: git@vger.kernel.org
Subject: Re: Trying to get GIT running on SCO OpenServer
Date: Thu, 24 Jan 2008 11:23:38 -0500 [thread overview]
Message-ID: <20080124162338.GC17244@yugib.highrise.ca> (raw)
In-Reply-To: <20080123212613.GN2230@yugib.highrise.ca>
[-- Attachment #1: Type: text/plain, Size: 2617 bytes --]
OK, piling hack upon hack to get things to work, I've got 4 tests that
don't pass:
-rwxr-xr-x 1 aidan group 5733 Jan 23 20:57 t/t5302-pack-index.sh
-rwxr-xr-x 1 aidan group 4204 Dec 4 15:21 t/t5400-send-pack.sh
-rwxr-xr-x 1 aidan group 4321 Dec 4 15:21 t/t7003-filter-branch.sh
-rwxr-xr-x 1 aidan group 16846 Jan 23 20:57 t/t9500-gitweb-standalone-no-errors.sh
git-pack-objects is segfaulting:
~/software/git.git/t/trash$ git-pack-objects test < obj-list
Counting objects: 102, done.
Compressing objects: 100% (101/101), done.
Segmentation Fault
Stack trace:
SIGNALED 11 (segv code[SEGV_MAPERR] address[0xbff68008]) in p1
184: <no source text available>
debug> stack
Stack Trace for p1, Program git-pack-objec
*[0] find_packed_object(presumed: 0, 0, 0xc) [�\@builtin-pack-objects.c@184]
[1] write_one(presumed: 0xc, 0, 0) [�\@builtin-pack-objects.c@512]
[2] write_pack_file(presumed: 0x8049364, 0, 0) [�\@builtin-pack-objects.c@628]
[3] cmd_pack_objects() [�\@builtin-pack-objects.c@2245]
Before I dig too deeply, does that look familiar to anyone?
Just FYI, my current stack of hacks is:
HACK: BROKEN_FOPEN
HACK: BROKEN_VSNPRINTF
HACK: strtoul
NO_RSYNC to avoid mkdtemp
An interesting one is the strtoul HACK:
diff --git a/builtin-unpack-objects.c b/builtin-unpack-objects.c
index 1e51865..2c2e187 100644
--- a/builtin-unpack-objects.c
+++ b/builtin-unpack-objects.c
@@ -368,7 +368,11 @@ int cmd_unpack_objects(int argc, const char **argv, const char *prefix)
hdr->hdr_version = htonl(strtoul(arg + 14, &c, 10));
if (*c != ',')
die("bad %s", arg);
- hdr->hdr_entries = htonl(strtoul(c + 1, &c, 10));
+{ /* Another ugly SCO hack */
+char*d;
+ hdr->hdr_entries = htonl(strtoul(c + 1, &d, 10));
+c = d;
+}
if (*c)
die("bad %s", arg);
len = sizeof(*hdr);
Is this just a *completely* broken compiler? With out this hack,
"c" is set to something farther ahead then the null at the end of the
"--pack-objects=2,10", and the if (*c) test obviously fails (and the
value read by the strtoul isn't correct either).
I've verified that the c *is* ",10" before entering that line... and I
can't see any reason why that wouldn't "just work", but hey, this is
SCO.
a.
--
Aidan Van Dyk Create like a god,
aidan@highrise.ca command like a king,
http://www.highrise.ca/ work like a slave.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2008-01-24 16:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 21:26 Trying to get GIT running on SCO OpenServer Aidan Van Dyk
2008-01-23 23:48 ` Johannes Schindelin
2008-01-24 0:17 ` Jakub Narebski
2008-01-24 0:25 ` Junio C Hamano
2008-01-24 2:33 ` H. Peter Anvin
2008-01-24 2:48 ` Junio C Hamano
2008-01-24 2:50 ` Linus Torvalds
2008-01-24 3:01 ` Luke Lu
2008-01-24 3:19 ` Linus Torvalds
2008-01-24 16:23 ` Aidan Van Dyk [this message]
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=20080124162338.GC17244@yugib.highrise.ca \
--to=aidan@highrise.ca \
--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