gdb/1945: BFD: bfd_cache_lookup_worker GNU/Linux GCC C++

ted@midg3t.net ted@midg3t.net
Sat May 14 18:18:00 GMT 2005


>Number:         1945
>Category:       gdb
>Synopsis:       BFD: bfd_cache_lookup_worker GNU/Linux GCC C++
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat May 14 18:18:00 UTC 2005
>Closed-Date:
>Last-Modified:
>Originator:     ted@midg3t.net
>Release:        GNU gdb 6.3
>Organization:
>Environment:
Linux retaliate 2.6.11.6 #3 Mon Apr 11 22:28:24 EST 2005 i686 unknown unknown GNU/Linux
gcc version 3.4.3
This GDB was configured as "i686-pc-linux-gnu".
>Description:
Had finished a gdb session, got an apparently non-fatal error message from BFD. I can't tell if it happened as part of GDB's shutdown process or perhaps something else. I've never seen any mention of BFD before. Have been running this configuration for several weeks (most recent change would've been kernel update).

I suspect this is probably not a GDB bug, however it's the most logical assumption for me based on what I saw. If I have reported it to the wrong place, _please_ let me know via email so I can send it to the right people.

-----start of output-----
Program received signal SIGABRT, Aborted.
0x4014d1b1 in kill () from /lib/libc.so.6
(gdb) quit
The program is running.  Exit anyway? (y or n) y
BFD: BFD 2.15.93 20041018 internal error, aborting at cache.c line 495 in bfd_cache_lookup_worker

BFD: Please report this bug.

ted@retaliate:quux$
----end of output----

The shell I was returned to seemed to be fully functional.
>How-To-Repeat:
Unsure (sorry!)
>Fix:
Unknown
>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the Gdb-prs mailing list