From: Richard Wallman <r_wallman@yahoo.co.uk>
To: Linux 8086 <linux-8086@vger.kernel.org>
Subject: Adventure - the answer to what went wrong?
Date: Thu, 12 Dec 2002 19:11:11 +0000 (GMT) [thread overview]
Message-ID: <200212121911.gBCJB75G012842@eddie.loc> (raw)
In-Reply-To: <1039651196.1847.43.camel@Castle.goembel>
Gave it a bit of thought today, and I think I know what happened.
Looking at the libc sources, it looks like the strcmp and strncmp
functions assume that both strings are in the same 64Kb segment. (There
may be other functions that make this assumption as well, but I haven't
really looked).
Looking at the file sizes, the "advent" program is 84Kb when compiled
using bcc.
I put forward the theory that it fails because the two strings are not
in the same 64Kb segment. The reason no-one has found this problem
before is that so far all of the binaries have been <64Kb in size.
Still, looks like it's been fixed now, but if anyone was wondering why
their port of their favourite app failed, that may be the reason.
--
Richard Wallman
http://www.murkygoth.uklinux.net/elks
next prev parent reply other threads:[~2002-12-12 19:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 13:07 ELKS port of Adventure - help needed :) Paul Nasrat
2002-12-11 8:19 ` Phil Goembel
2002-12-11 21:27 ` Richard Wallman
2002-12-11 22:22 ` Richard Wallman
2002-12-11 22:46 ` Richard Wallman
2002-12-11 22:51 ` Paul Nasrat
2002-12-11 23:59 ` Phil Goembel
2002-12-12 7:39 ` Paul Nasrat
2002-12-12 8:18 ` Paul Nasrat
2002-12-12 19:11 ` Richard Wallman [this message]
2002-12-12 20:21 ` Adventure - the answer to what went wrong? Harry Kalogirou
2002-12-12 20:52 ` Alan Cox
2002-12-12 20:27 ` Dan Olson
2002-12-12 20:29 ` Harry Kalogirou
2002-12-12 20:41 ` Dan Olson
2002-12-12 21:15 ` Alan Cox
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=200212121911.gBCJB75G012842@eddie.loc \
--to=r_wallman@yahoo.co.uk \
--cc=linux-8086@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