Date: Sun, 9 Apr 2000 08:28:27 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Pierre Muller <muller AT cerbere DOT u-strasbg DOT fr>
cc: djgpp-workers AT delorie DOT com
Subject: Re: Compiling GDB for DJGPP
In-Reply-To: <200004061657.SAA02787@cerbere.u-strasbg.fr>
Message-ID: <Pine.SUN.3.91.1000409082813.7469E-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Thu, 6 Apr 2000, Pierre Muller wrote:

> First, I wolud like to state that indeed configure works without problems !

Thanks for testing this!

Was this on DOS or on Windows 9X?

>   Second, I wanted to use  -gstabs option instead of -g 
> (the is a line count limitation with -g that is overflooded)

I don't recommend this change.  SYMIFY doesn't support stabs, so you
cannot use crash tracebacks efficiently.

The overflow of the line info is harmless: what the linker does is
simply to ignore the extra line info entries, and it usually hits the
last file in the link process, which is in gnu-regex.c or some
such--hardly a module that you would want to debug.

I have on my todo list to stop linking in all the modules for which we
don't have any use, like dwarfread.c, os9read.c, dbxread.c, and
others; this should solve the overflow problem.  If someone feels like
working on that, please do.