Xref: utzoo comp.unix.microport:201 comp.unix.questions:6020
Path: utzoo!mnetor!uunet!husc6!bloom-beacon!mit-eddie!uw-beaver!tektronix!reed!percival!nerd
From: nerd@percival.UUCP (Michael Galassi)
Newsgroups: comp.unix.microport,comp.unix.questions
Subject: Re: SDB out of memory?
Message-ID: <1142@percival.UUCP>
Date: 9 Mar 88 08:46:13 GMT
References: <163@bdt.UUCP> <633@ncrcce.StPaul.NCR.COM>
Reply-To: nerd@percival.UUCP (Michael Galassi)
Organization: Percy's UNIX, Portland, OR.
Lines: 31

In article <633@ncrcce.StPaul.NCR.COM> mercer@ncrcce.StPaul.NCR.COM (PUT YOUR NAME HERE) writes:
>In article <163@bdt.UUCP> david@bdt.UUCP (David Beckemeyer) writes:

>>What can be done when sdb gives the following fatal error message:
>>"Cannot allocate space for internal symbol table; Goodbye."
>>I can't find anything in my Microport manuals. Thanks in advance.

I have run into this when I work with VERY large programs in which
all (or many) of the files are compiled with the "-g" flag.  My solution
is to not use the "-g" flag on modules that have reached some reasonable
level of stability.

>I've had this happen to me,  usually when I inadvertently call:
>sdb sourcefile.c
>instead of the loadable program
>sdb a.out
>My guess is you made the same mistake.

I hope not.  That could lead to problems.  One solution to this is
to just type "sdb<c/r>", the defaults for the executable's name,
the core file's name and the source directory are:
a.out
core
.
so typicaly you don't even need any parameters.

-michael
-- 
        Michael Galassi           | If my opinions happen to be the same as
...!tektronix!tessi!percival!nerd | my employer's it is ONLY a coincidence,
...!uunet!littlei!percival!nerd   | of cource coincidences DO happen.