Re: objdump --debugging goes into infinite loop

[Andrew Pimlott]

On Tue, Feb 18, 2003 at 09:21:55AM +1030, Alan Modra wrote:
> Works OK for me.  It's possible that some part of objdump has been
> mis-compiled on your system.

This is rather shocking to me, but you may be right.  Here is a
suggestion that this is a compiler or other low-level error:

    Program received signal SIGINT, Interrupt.
    debug_get_real_type (handle=0x80d4658, type=0x80f9d70, list=0x0)
        at ../../binutils/debug.c:2186
    2186      for (l = list; l != NULL; l = l->next)
    (gdb) bt 
    #0  debug_get_real_type (handle=0x80d4658, type=0x80f9d70, list=0x0)
        at ../../binutils/debug.c:2186
    #1  0x0805321b in debug_class_type_samep (info=0x80d4658, t1=0x8103408, 
        t2=0x80ff3f0) at ../../binutils/debug.c:3463
    ...
    (gdb) p list
    $2 = (struct debug_type_real_list *) 0xbffff430

The backtrace says list is NULL, and debug_get_real_type is called
with a constant NULL, and nothing in the function changes list, yet
at the time of the signal (generated my me hitting ctrl-c in the
debuger) list has a value, list->next == list.  Nor do I see any
avenue for corruption.  Is there any sane explanation for this?

I would really appreciate any help, because this has me totally
mystified.

Andrew