Date: Mon, 14 Aug 2000 19:04:32 +0200 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: lauras AT softhome DOT net Message-Id: <7458-Mon14Aug2000190432+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: <3997D6A2.59F4F2C6@softhome.net> (message from Laurynas Biveinis on Mon, 14 Aug 2000 13:23:14 +0200) Subject: Re: Symify crash References: <3997D6A2 DOT 59F4F2C6 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 Precedence: bulk > Date: Mon, 14 Aug 2000 13:23:14 +0200 > From: Laurynas Biveinis > > Maybe it is time to switch to stabs as a default debugging format > and use Eli's bfdsymify? You don't need to switch to stabs in order to use bfdsymify. It understands all debug formats for which BFD was configured. That was the whole point of building it. > FWIW, I've been using it for three months without seeing a single > problem. I have a couple of unresolved issues with it: for example, it sometimes (very rarely) prints wrong line numbers. Also, I didn't see any simple way of making the part which reads the traceback from screen system-independent (more accurately, with what to replace it on other systems), which prevented me from sending the patches to the Binutils maintainer. There's also a (rather trivial) matter of changing the display code as we did in SYMIFY for v2.03, so that long C++ names and/or long source file names don't blow up the stack and don't wrap around the display line. Unfortunately, I have no time lately to finish this, so if someone wants to take over, please do.