home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.ibm.pc.programmer:393 comp.os.msdos.programmer:9193
- Newsgroups: comp.sys.ibm.pc.programmer,comp.os.msdos.programmer
- Path: sparky!uunet!spool.mu.edu!agate!dog.ee.lbl.gov!hellgate.utah.edu!peruvian.utah.edu!msmith
- From: msmith%peruvian.utah.edu@cs.utah.edu (Matthew Smith)
- Subject: Re: Group DGROUP exceeds 64K
- Date: 9 Sep 92 10:54:43 MDT
- Message-ID: <1992Sep9.105443.19241@hellgate.utah.edu>
- Organization: University of Utah CS Dept
- References: <1992Sep4.213550.13151@pollux.lu.se>
- Lines: 29
-
- In article <1992Sep4.213550.13151@pollux.lu.se> lars_s@gemini.ldc.lu.se writes:
- >I'm using Borland C++ version 3.0 in large memory model and are trying to
- >link a couple of modules. I got this message from TLINK:
- >
- > Error: Group DGROUP exceeds 64K
- >
- >Tools and Utilities Guide says:
- >A group exceeded 64K bytes when the segments of the group wwere combined.
- >
- >Any hint or workaround to solve my problem are appreciated.
-
- Are you using C++ specific code? If so, you can use the -Vf switch for BCC,
- or look for a switch in the IDE which moves the C++ virtual tables out of
- the data segment.
-
- Basically, this error means that your global variable area has exceeded 64k.
- Evidently, Borland puts their virtual tables (or at least some information
- concerning them) into this segment.
-
- >Thanks in advance,
- > Lars
- >--------------------------
- >Lars.Sigebo@ldc.lu.se
- >Lund University Computing Center, Sweden
-
-
- Matt Smith
- msmith@peruvian.utah.edu
- Student - University of Utah Department of Computer Science
-