This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug cli/19551] New: weird "reading symbols" output


https://sourceware.org/bugzilla/show_bug.cgi?id=19551

            Bug ID: 19551
           Summary: weird "reading symbols" output
           Product: gdb
           Version: unknown
            Status: NEW
          Severity: normal
          Priority: P2
         Component: cli
          Assignee: unassigned at sourceware dot org
          Reporter: tromey at sourceware dot org
  Target Milestone: ---

I attach'd to a firefox process.
I have some system debuginfo installed, but not everything.

I saw this in the voluminous output from gdb:

Reading symbols from /lib64/libgconf-2.so.4...Reading symbols from
/lib64/libgconf-2.so.4...(no debugging symbols found)...done.
(no debugging symbols found)...done.


I think this is a bug for two reasons.
First, it mentions the same file twice.
Second, it is badly formatted.


I think that the second mention of the file name comes from the mini
debug info.  In this case the "no debugging symbols found" text is also
somewhat erroneous.

One way to make this prettier would be something like:

Reading symbols from /lib64/libgconf-2.so.4... found mini debug info.
Reading symbols from /lib64/libgconf-2.so.4 mini debug info...done.

This could be extended to deal with separate debug info as well.
Ideally "no debugging symbols found" would only be printed when truly
nothing was found.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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