Date:	Sun, 13 Aug 2000 21:45:25 +0200
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	lauras AT softhome DOT net
Message-Id:	<2593-Sun13Aug2000214525+0300-eliz@is.elta.co.il>
X-Mailer:	Emacs 20.6 (via feedmail 8.2.emacs20_6 I) and Blat ver 1.8.5b
CC:	djgpp AT delorie DOT com
In-reply-to:	<3996E3F4.C9B37F8B@softhome.net> (message from Laurynas Biveinis
	on Sun, 13 Aug 2000 20:07:48 +0200)
Subject:	Re: Symify crash
References:	<3 DOT 0 DOT 5 DOT 32 DOT 20000813122244 DOT 007c0c00 AT pop DOT mail DOT yahoo DOT com> <3405-Sun13Aug2000163046+0300-eliz AT is DOT elta DOT co DOT il> <3996E3F4 DOT C9B37F8B AT softhome DOT net>
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

> Date: Sun, 13 Aug 2000 20:07:48 +0200
> From: Laurynas Biveinis <lauras AT softhome DOT net>
> 
> I've seen them too. I think they're caused by limitations
> of current default debugging format. If linker produces
> warning about line number overflow (I might be wrong; I barely
> recall that right now) for big program, and if it crashes, then
> symify crashes too.

The only program where I've seen the linker to complain about line
number overflow is GDB.  OTOH, crashes of SYMIFY I usually see for
Emacs, where the number of lines does not overflow at all.

It *is* true, however, that only large programs seem to trigger this.
I suspect some uninitialized variable in the code which reads symbols,
before they are sorted.

Someone should catch the offending code red-handed.

- Raw text -