news@crdgw1.crd.ge.com (USENET News System) (09/09/90)
libraries. When I compile (MSC6.0) more than 4 or 5 routines with
debugger information (-Zi) I get a linker error message telling me
that symbol table space is exhausted. Although it is somewhat painful,
I can live with only a few routines compiled with debug information.
I'm more than a little concerned that pretty soon I will not be able
to link at all as the program lacks a substantial amount of functionality.
The executable program will run in 230K.
From: dixon@sagittarius.crd.ge.com (walt dixon)
Path: sagittarius!dixon
Am I correct in assuming that MS Link keeps the entire symbol table
in memory? I understand that there are entries for modules, segments,
groups, etc., but I'm having a hard time figuring out where all the
space is going. Just how much memory is requried for each symbol?
Is there any way of using extended memory for the symbol table?
The only other alternative I can come up with is to switch to a third
party linker. Does anyone have any recommendations? The requirements
I have are that the linker understand MS Library format, work with MSC
6.0, and work with code view.
Thanks in advance.
Walt Dixon {internet: dixon@crd.ge.com }
{us mail: ge-crd }
{ po box 8 }
{ schenectady, ny 12301 }
{phone: 518-387-5798 (W) }
{ 518-875-6203 (H) }
Walt Dixon dixon@crd.ge.com