Memory allocation problems using Bc++3.1

Article View: comp.os.ms-windows.programmer.misc

Article #1793

Back to comp.os.ms-windows.programmer.misc Previous Next

#1793

From: Chander Raja
Date: Wed, 23 Dec 1992 06:20

16 lines
1125 bytes

I am new to Windows programming and OWL. Till a few days ago, I
had no problems compiling my program under the small memory model.
But as I kept adding more code, the linker would give me 
unfriendly " Segment _TEXT exceeds 64K"s . So I switched to the
large memory model. But now, the program crashes a lot, mostly
in the constructor of a class before executing even a single line of it.
I have traced it to malloc.

Is there a problem with Borland's memory management routines under
OWL? I know that they have overloaded the operators new and delete
globally. Has someone tried to overload new and delete using the
global heap? If so please post it.

Thanks in advance.
-Chander
chander@access.digex.com

Technical Details

Message-ID: <1h90f8INNs0c@mirror.digex.com>

Path: arc1-ca.pugleaf.net!sparky!uunet!digex.com!chander

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!sparky!uunet!digex.com!chander
From: chander@access.digex.com (Chander Raja)
Newsgroups: comp.os.ms-windows.programmer.misc
Subject: Memory allocation problems using Bc++3.1
Date: 23 Dec 1992 06:20:24 GMT
Organization: Express Access Online Communications, Greenbelt, MD USA
Lines: 16
Distribution: world
Message-ID: <1h90f8INNs0c@mirror.digex.com>
NNTP-Posting-Host: access.digex.com