Date: Fri, 16 Nov 2001 12:50:15 +0200
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: dj AT delorie DOT com
Message-Id: <8296-Fri16Nov2001125015+0200-eliz@is.elta.co.il>
X-Mailer: emacs 21.1.50 (via feedmail 8 I) and Blat ver 1.8.9
CC: djgpp AT delorie DOT com, Dave Dribin <yhdrib AT yahoo DOT com>
In-reply-to: <9t1k89$8lu$1@bob.news.rcn.net> (message from Dave Dribin on 15
	Nov 2001 23:48:25 GMT)
Subject: Re: symify crash
References:  <9t1k89$8lu$1 AT bob DOT news DOT rcn 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
Precedence: bulk

> From: Dave Dribin <yhdrib AT yahoo DOT com>
> Newsgroups: comp.os.msdos.djgpp
> Date: 15 Nov 2001 23:48:25 GMT
> 
> I am having a problem where symify is crashing when it is being run.
> This article mentions that it is a known problem in DJGPP v2.03:
> 
>   http://groups.google.com/groups?hl=en&selm=9743-Sat30Jun2001092828%2B0300-eliz%40is.elta.co.il
> 
> However, it points to a new symify.exe at this URL:
> 
>   ftp://is.elta.co.il/pub/symify.exe
> 
> I cannot get to this new symify.exe (the server isn't allowing
> anonymous logins)

Yep, the sysadmins disabled anon ftp access, due to malicious
hackers' abuse.  It's a sad world we are living in...

> Is a fixed symify.exe available anywhere else?

I've uploaded it to DJ Delorie's server, in the /incoming directory.
DJ, could you please move it to pub/djgpp/beta, where users could get
it?  (I don't have write access to that directory.)

> I really need symify. :) It
> seems to happen with gcc 2.95.3 and gcc 2.95.2.  One of the libraries
> I depend on does not compile with gcc 3.0.2, so upgrading is not yet
> an option.

I don't think upgrading GCC would have helped you.  The crashes happen
because a certain function in libdbg.a (which is linked into
symify.exe) could not cope well with large executables where the
number of source lines recorded in the debug info is very large,
especially if it overflows the COFF 64K-lines limit.  The fix for the
bug is not in symify.c, it's in that library function, and the code
generated by GCC has nothing to do with this.