Path: csiph.com!weretis.net!feeder8.news.weretis.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Paul Edwards <mutazilah@gmail.com>
Newsgroups: comp.os.os2.programmer.misc
Subject: limit
Date: Thu, 14 Mar 2024 01:56:33 +0800
Organization: A noiseless patient Spider
Lines: 42
Message-ID: <usspco$12mfq$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Wed, 13 Mar 2024 17:56:40 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="6dbf7e8cafa7f2c7da7d5bdbe69ce84b"; logging-data="1137146"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18hEYPU7xDHrR9PEQQTf6OtRNKXub0UlMI="
User-Agent: Mozilla/5.0 (OS/2; Warp 4.5; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
Cancel-Lock: sha1:VsXVH2TVbNGzxM06K4uT8rnwQ98=
X-Mozilla-News-Host: news://news.eternal-september.org:119
Xref: csiph.com comp.os.os2.programmer.misc:1908

I noticed this in one of my crashes:

03-14-2024  00:00:43  SYS3175  PID 006f  TID 0001  Slot 003f
P:\DOS\GCCWIN.EXE
c0000005
0028c43e
P1=00000002  P2=0024a429  P3=XXXXXXXX  P4=XXXXXXXX
EAX=65746e69  EBX=0024a445  ECX=001392f3  EDX=0024a429
ESI=0024a429  EDI=0000001d
DS=0053  DSACC=d0f3  DSLIM=5fffffff
ES=0053  ESACC=d0f3  ESLIM=5fffffff
FS=150b  FSACC=00f3  FSLIM=00000030
GS=0000  GSACC=****  GSLIM=********
CS:EIP=005b:0028c43e  CSACC=d0df  CSLIM=5fffffff
SS:ESP=0053:0035766c  SSACC=d0f3  SSLIM=5fffffff
EBP=00357678  FLG=00010287

GCCWIN.EXE 0001:0027c43e



I see that DS has a limit of 5fff ffff which is basically 1.5 GB.

But I thought without OBJ_ANY I got 512 MiB max, and
with OBJ_ANY I could potentially access 4 GiB.

So where is that limit coming from?

Is there some flag in the LX executable I need to
set, as well as using OBJ_ANY?

BTW, I suspect I can implement PDPCLIB for OS/2
the same way I did for MVS, which is use OBJ_ANY
for any application request via malloc(), but for
any internal use, ie fopen buffers to be transferred
to DosRead/DosWrite I would do a different malloc
that doesn't have OBJ_ANY.

So user applications become effectively unrestricted,
without any odd functions like SafeDosOpen.

BFN. Paul.