Bug 8806 - Error while reading shared library symbols
Summary: Error while reading shared library symbols
Status: RESOLVED INVALID
Alias: None
Product: gdb
Classification: Unclassified
Component: c++ (show other bugs)
Version: unknown
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-07-01 10:08 UTC by nuclear
Modified: 2010-01-20 05:25 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description nuclear 2004-07-01 10:08:00 UTC
[Converted from Gnats 1701]

Fedora Core 2 + KDevelop 3.0.3 = gdb message: Error while reading shared library symbols: : No such file or directory.
(gdb) backtrace 
Error while reading shared library symbols:
: No such file or directory.

Stopped due to shared library event
#0  0x00a68480 in _dl_debug_state () from /lib/ld-linux.so.2
#1  0x00a5d961 in dl_main () from /lib/ld-linux.so.2
#2  0x00a6ae14 in _dl_sysdep_start () from /lib/ld-linux.so.2
#3  0x00a5cac0 in _dl_start () from /lib/ld-linux.so.2
#4  0x00a5c7c7 in _start () from /lib/ld-linux.so.2

Release:
unknown

Environment:
Error while reading shared library symbols
Comment 1 drow@false.org 2004-07-01 12:45:49 UTC
From: Daniel Jacobowitz <drow@false.org>
To: nuclear@bel.ru
Cc: gdb-gnats@sources.redhat.com
Subject: Re: c++/1701: Error while reading shared library symbols
Date: Thu, 1 Jul 2004 08:45:49 -0400

 > (gdb) backtrace 
 > Error while reading shared library symbols:
 > : No such file or directory.
 > 
 > Stopped due to shared library event
 > #0  0x00a68480 in _dl_debug_state () from /lib/ld-linux.so.2
 > #1  0x00a5d961 in dl_main () from /lib/ld-linux.so.2
 > #2  0x00a6ae14 in _dl_sysdep_start () from /lib/ld-linux.so.2
 > #3  0x00a5cac0 in _dl_start () from /lib/ld-linux.so.2
 > #4  0x00a5c7c7 in _start () from /lib/ld-linux.so.2
 
 What were you debugging?  What have you done in this debugging session? 
 Is there anything special set in your environment?  There's nothing in
 the bug report that gives me a clue what is wrong.
 
 -- 
 Daniel Jacobowitz
Comment 2 Tom Tromey 2010-01-20 05:25:48 UTC
5 years without feedback.