Article View: bit.listserv.appc-l
Article #445More questions on CM/2 in 2.1 and shared memory
From: Tom Thomas
Date: Tue, 07 Dec 1993 03:24
Date: Tue, 07 Dec 1993 03:24
16 lines
1460 bytes
1460 bytes
I guess I should have asked a broader question regarding CM/2 and OS/2 2.1 memory allocation. Under the 16-bit version (including ES under OS/2 2.x), I had to allocate tiled memory and use the fALLOCSHR flag, which sets OBJ_GIVABLE and OBJ_GETTABLE (among others). The CM/ES daemons would get access to these regions (increasing their usage count) upon usage of APPC (CPI-C) APIs. This caused my programs to be prone to memory leaks (through multiple invocations) unless I took explicit precautions. My general question is: Is this all still true with CM/2 1.0 and above? Can I allocate 32-bit regions? Can I use automatic (stack) storage? Again - thanks in advance for your response(s). Tom Thomas
Technical Details
Message-ID:
<9312070324.AA12714@ponder>Path:
arc1-ca.pugleaf.net!gmd.de!newsserver.jvnc.net!howland.reston.ans.net!paladin.american.edu!auvm!PONDER.CSCI.UNT.EDU!thomasShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10aed9,5e34d03390c0acd6,start X-Google-Attributes: gid10aed9,public X-Google-ArrivalTime: 1993-12-11 15:33:44 PST Path: arc1-ca.pugleaf.net!gmd.de!newsserver.jvnc.net!howland.reston.ans.net!paladin.american.edu!auvm!PONDER.CSCI.UNT.EDU!thomas Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU Newsgroups: bit.listserv.appc-l Return-Path: <@AUVM.AMERICAN.EDU:owner-appc-l@AUVM.AMERICAN.EDU> Return-Path: <@AUVM.AMERICAN.EDU:thomas@PONDER.CSCI.UNT.EDU> Message-ID: <9312070324.AA12714@ponder> Date: Mon, 6 Dec 1993 21:24:35 -0600 Sender: APPC Discussion List <APPC-L@AUVM.BITNET> From: Tom Thomas <thomas@PONDER.CSCI.UNT.EDU> Subject: More questions on CM/2 in 2.1 and shared memory Lines: 15