Date: Wed, 21 Jul 1999 10:52:08 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
cc: djgpp-workers AT delorie DOT com
Subject: Re: Bizarre debugging format problem
In-Reply-To: <Pine.LNX.3.93.990720153851.212G-100000@acp3bf>
Message-ID: <Pine.SUN.3.91.990721105127.7757D-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


Regarding this thread on c.o.m.d., did someone ever look into the guts
of the BFD function coff_find_nearest_line (it's in bfd/coffgen.c)
from Binutils?  As I said, it fails miserably for some very common
cases where our libdbg.a functions work.  I can spot several wrong
assumptions in the code, but I'm not sure they explain all the
failures I've seen, and I didn't yet have enough time to debug this.

To test, compare output of addr2line program with what SYMIFY prints
for the same image.