Date:	Mon, 1 Feb 1999 18:47:45 +0100
From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Message-Id:	<199902011747.SAA11228@acp3bf.physik.rwth-aachen.de>
To:	djgpp AT delorie DOT com
Subject:	Re: performance
Newsgroups:	comp.os.msdos.djgpp
Organization:	RWTH Aachen, III. physikalisches Institut B
X-Newsreader:	TIN [version 1.2 PL2]
Reply-To:	djgpp AT delorie DOT com

[I wonder why you posted this as a reply to the 'performance' thread...]

In article <36B5E345 DOT 37E02654 AT ameritech DOT net> you wrote:
> DJ,

[ You reached the newsgroup, not DJ Delorie himself...]

> related ;-) stumper.  We are past our due date and this has stopped
> all development!

OK, then let me fire off a really quick reply:

> Error: e:/djgpp/bin\ld.exe: Posterm.exe: warning: .text: line number
> overflow: 0x11a1c > 0xffff

You've got more than 64K (0xffff) of debuggable source line numbers in
your program. The COFF debugging info format can't deal with that.

Possible workarounds:

1) Use option '-gstabs' instead of '-g' (and suitable versions of gcc
and binutils to allow using it). Stabs debug info does not have this
limitation. Drawback: debuggers other than GDB might have problems
understanding this type of debug info.

2) For a very short-term hack, compile some of your modules without
debugging infos. You're only a little bit beyond the barrier, so this
might help you over the time you need to get and install current
versions of gcc and binutils.

--
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -