🚀 go-pugleaf

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01C21054.51413380
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,

I debugged a (generated) C-source file having 67735 lines. The problem
arises=20
in line ~67600, but gdb showed me (with the list command) the line =
~2400.
I looked in the symbol table (produced by maintprint symbol) and saw =
that
in the "Line table", after entry for line 65533 the entry for line 4
follows.

It seems to me that the line number is stored by gdb only as an =
unsigned 2
byte integer. (gcc showed error messages in that aera with the correct =
line
number).

I use:
	gdb 5.1.1, configuread for a i386-suse-linux
	gcc 2.95.3 20010315 (SuSE)
	linux 2.4.18-4GB i686 =20
all taken from the SuSE 8.0 Intel-Linux distribution.

Please find enclosed a "large" file producing the bug. Basically it's a =
lot
of new lines followed by a "int i =3D 10/0;" one-line-main function.
 =09
With best regards
J=FCrgen Vollmer

 <<xx.c.gz>>=20
=20
----
Dr. J=FCrgen Vollmer <vollmer@cocolab.de>
CoCoLab
c/o Dresdner Bank AG
IS-STA Software-Technologie und -Architektur f=FCr
Allianz Gruppe Deutschland
Application Development Architecture Services
Repository Management

D-60301 Frankfurt am Main
voice: (+49) 069 / 263 85 122
email: Juergen.Vollmer@Dresdner-Bank.com



------_=_NextPart_000_01C21054.51413380
Content-Type: application/octet-stream;
	name="xx.c.gz"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="xx.c.gz"

H4sICNxZBD0AA3h4LmMA7ckxCsJQFEXB/q3ilkYEk1pciVh8UsRfmCKIjbh3dR3OVAdOFQAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAD/7d76ml1fH2nbMh8y39qW/befl+tQr0p+r+ecacwx46ne9QHvgItoThABAA==

------_=_NextPart_000_01C21054.51413380--