From: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
To: <djgpp-workers AT delorie DOT com>
Subject: Re: bfdsymify
Date: Mon, 9 Jul 2001 19:22:17 +0200
Message-ID: <CAEGKOHJKAAFPKOCLHDIIEDOCFAA.tim.van.holder@pandora.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <Pine.SUN.3.91.1010709132923.7330B-100000@is>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> When this issue surfaced some time ago, DJ suggested to submit the
> program for inclusion in the Binutils package, so that it will be always
> available withe every port of Binutils.  But this requires that bfdsymify
> be portable to platforms other than DJGPP, which is not easy, given the
> screen capture code.  (Btw, do GNU/Linux systems have a device yet that

Well, yes - but you could probably start it out as a DJGPP-only tool (so
that it only gets built on DJGPP), as there are probably few systems that
print such a traceback (and for smaller tasks, addr2line suffices).
Plus, other systems may dump such a traceback in a redirectable way, so
extending bfdsymify to be able to read the traceback from a text file would
be a more useful feature than trying to implement generic screen-reading.