Date:	Sat, 01 Jun 2002 16:44:15 +0300
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	"deckerben" <deckerben AT freenet DOT de>
Message-Id:	<6436-Sat01Jun2002164414+0300-eliz@is.elta.co.il>
X-Mailer:	emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9
CC:	djgpp AT delorie DOT com
In-reply-to:	<3cf8be28$0$8330$9b622d9e@news.freenet.de> (deckerben@freenet.de)
Subject:	Re: "line number overflow"
References:	<3cf8be28$0$8330$9b622d9e AT news DOT freenet DOT de>
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> From: "deckerben" <deckerben AT freenet DOT de>
> Newsgroups: comp.os.msdos.djgpp
> Date: Sat, 1 Jun 2002 14:43:36 +0200
> 
> warning: .text: line number overflow: 0x194f9 > 0xffff
> 
> I haven't noticed a big problem in the executable as a result of the
> warning.

In general, you can disregard this warning.  It means that the number
of source lines for which the linker needs to put debug info into the
executable is more than the COFF debug info format allows (whcih is
64K lines total).  What the linker does is omit the debug info for
the lines beyond the first 64K.

This only affects debugging, it has no effect on the produced code.

To be able to debug such large programs, compile with -gstabs+ or -ggdb3
instead of a mere -g.  This requests stabs or DWARF2 debug info
format, which isn't limited to 64K lines in a program.

> But the problem is a little more serious with dxe2gen, which will
> not create the library AT ALL when this error occurs.

Try compiling without -g, and I think the problem might go away.

- Raw text -