From: Harry Kalogirou <harkal@gmx.net>
To: Richard Wallman <r_wallman@yahoo.co.uk>
Cc: Linux 8086 <linux-8086@vger.kernel.org>
Subject: Re: Adventure - the answer to what went wrong?
Date: 12 Dec 2002 22:21:13 +0200 [thread overview]
Message-ID: <1039724471.2746.21.camel@cool> (raw)
In-Reply-To: <200212121911.gBCJB75G012842@eddie.loc>
[-- Attachment #1: Type: text/plain, Size: 534 bytes --]
> 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).
They assume right! In ELKS DS=SS=ES.
By the way, the CVS ELKS tree solves many memory problems but requires a
patch to the linker that I posted here some time ago and never got in
the linker tree... :(
Harry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-12-12 20:21 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 ` Adventure - the answer to what went wrong? Richard Wallman
2002-12-12 20:21 ` Harry Kalogirou [this message]
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=1039724471.2746.21.camel@cool \
--to=harkal@gmx.net \
--cc=linux-8086@vger.kernel.org \
--cc=r_wallman@yahoo.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.