This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: buglet in binutils/debug.c


On Fri, Jun 16, 2000 at 05:41:49PM -0700, Aaron J. Grier wrote:
> --- binutils-2.9.5.0.37/binutils/debug.c.orig   Fri Jun 16 17:18:56 2000
> +++ binutils-2.9.5.0.37/binutils/debug.c        Fri Jun 16 17:28:16 2000
> @@ -2198,6 +2198,12 @@
>                    debug_get_type_name (handle, type));
>           return NULL;
>         }
> +      if (l->next == l)
> +        {
> +          fprintf (stderr,
> +                   _("debug_get_real_type: l->next == l, I'm in a loop\n"));
> +          break;
> +        }
>      }
>  
>    rl.next = list;
> 
> this is probably not an optimal solution, but I was getting into an
> endless loop when running m68k-rtems-objdump --debugging --disassemble
> and needed a quick fix.

I noticed this a year ago.  this problem still exists in
binutils-2.12.2, and in the current version of binutils, apparent for
m68k-rtems-elf when trying to objcopy from elf to ieee with --debugging.

any ideas where to start hunting this bug down?  it's certainly been
there long enough...

-- 
  Aaron J. Grier   |    Frye Electronics, Tigard, OR   |   aaron@frye.com
                       Of course unix clones exist...
                  How else are unix supposed to reproduce?


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]