[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Bug in GNU objdump 2.13.90 20021009
From: |
Michael Peter |
Subject: |
Bug in GNU objdump 2.13.90 20021009 |
Date: |
Wed, 9 Oct 2002 16:21:58 +0200 |
User-agent: |
Mutt/1.3.27i |
Hi,
we found erroneous behavior in objdump.
Trying to retrieve debug information with the -g switch
freezes objdump in an infinite loop.
objdump version: current cvs snapshot (oct 9,2002, GNU objdump 2.13.90 20021009)
configured with --enable-debug, no other special settings
older versions seem the be affected as well
(same behavior for GNU objdump 2.12.90.0.1 20020307 Debian/GNU
Linux)
command: objdump -g thread.o
thread.o available from
http://os.inf.tu-dresden.de/~peter/objdump-bug/thread.o
md5sum 9d101c53cd5aa18794ed2ddd571386fb
compiled with : g++ -c -MD -DCROSS -O2 -DARCH_X86 -DL4_API_L4V2
-nostdinc -Ikern -Ikern/ia32 -I. -Ilib/oskit -Ilib/lmm -I../kern -I../kern/ia32
-I../. -I../lib/oskit -I../lib/lmm -Iauto
-I/home/peter/FIASCO/stable-current/l4/include/x86/l4v2
-I/home/peter/FIASCO/stable-current/l4/include/x86
-I/home/peter/FIASCO/stable-current/l4/include
-I/home/peter/FIASCO/stable-current/l4/../oskit
-I/home/peter/FIASCO/stable-current/l4/../oskit/flux/c -I/home/drops/include
-I/home/drops/include/flux/c -march=i586 -fno-rtti -fno-exceptions -nostdinc
-O6 -fno-defer-pop -g -Wall auto/thread.cc -o thread.o
gcc version 2.95.4 20011002 (Debian prerelease)
behavior: freezes after some output
investigated: infinite traversing a ring linked list
backtrace generated by gdb:
Program received signal SIGINT, Interrupt.
0x080517e5 in debug_get_real_type (handle=0x80d3258, type=0x81031c8, list=0x0)
at debug.c:2187
2187 if (l->t == type)
(gdb) bt
#0 0x080517e5 in debug_get_real_type (handle=0x80d3258, type=0x81031c8,
list=0x0) at debug.c:2187
#1 0x080530fb in debug_class_type_samep (info=0x80d3258, t1=0x8107140,
t2=0x8107838) at debug.c:3462
#2 0x08052c85 in debug_type_samep (info=0x80d3258, t1=0x8107140, t2=0x8107838)
at debug.c:3270
#3 0x08052ab5 in debug_set_class_id (info=0x80d3258, tag=0x0, type=0x8107838)
at debug.c:3150
#4 0x08052459 in debug_write_class_type (info=0x80d3258, fns=0x80b3e60,
fhandle=0xbffffbdc, type=0x8107838, tag=0x0) at debug.c:2848
#5 0x08052036 in debug_write_type (info=0x80d3258, fns=0x80b3e60,
fhandle=0xbffffbdc, type=0x8107870, name=0x0) at debug.c:2714
#6 0x0805256e in debug_write_class_type (info=0x80d3258, fns=0x80b3e60,
fhandle=0xbffffbdc, type=0x8107ea0, tag=0x0) at debug.c:2889
#7 0x08052036 in debug_write_type (info=0x80d3258, fns=0x80b3e60,
fhandle=0xbffffbdc, type=0x8107ed8, name=0x0) at debug.c:2714
#8 0x0805231c in debug_write_type (info=0x80d3258, fns=0x80b3e60,
fhandle=0xbffffbdc, type=0x812fdd8, name=0x0) at debug.c:2787
#9 0x080526ce in debug_write_class_type (info=0x80d3258, fns=0x80b3e60,
fhandle=0xbffffbdc, type=0x81307b0, tag=0x811c598 "thread_t")
at debug.c:2945
#10 0x08052036 in debug_write_type (info=0x80d3258, fns=0x80b3e60,
fhandle=0xbffffbdc, type=0x81307e8, name=0x8130810) at debug.c:2714
#11 0x08051c22 in debug_write_name (info=0x80d3258, fns=0x80b3e60,
fhandle=0xbffffbdc, n=0x8130810) at debug.c:2544
#12 0x08051b69 in debug_write (handle=0x80d3258, fns=0x80b3e60,
fhandle=0xbffffbdc) at debug.c:2512
#13 0x0804d9c6 in print_debugging_info (f=0x40134200, dhandle=0x80d3258)
at prdbg.c:194
#14 0x0804c406 in dump_bfd (abfd=0x80d15b0) at ./objdump.c:2079
#15 0x0804c502 in display_bfd (abfd=0x80d15b0) at ./objdump.c:2129
#16 0x0804c61a in display_file (
filename=0xbffffe20 "/home/peter/public_html/objdump-bug/thread.o",
target=0x0) at ./objdump.c:2184
#17 0x0804d8b2 in main (argc=3, argv=0xbffffd14) at ./objdump.c:2923
A complete typescript is also available from:
http://os.inf.tu-dresden.de/~peter/public_html/objdump-bug/typescript
Yours,
Michael
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Bug in GNU objdump 2.13.90 20021009,
Michael Peter <=