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 shlibs/15944] New: "info target" output could be cleaner


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

            Bug ID: 15944
           Summary: "info target" output could be cleaner
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: shlibs
          Assignee: unassigned at sourceware dot org
          Reporter: dje at google dot com

The output of "info target" could be cleaner.

(gdb) info target
Symbols from "home/dje/hello.x64".
Unix child process:
        Using the running image of child process 20343.
        While running this, GDB does not access memory from...
Local exec file:
        `/home/dje/hello.x64', file type elf64-x86-64.
        Entry point: 0x4006d0
        0x0000000000400238 - 0x0000000000400254 is .interp
        0x0000000000400254 - 0x0000000000400274 is .note.ABI-tag
        0x0000000000400274 - 0x0000000000400298 is .note.gnu.build-id
        [... all the sections of "Local exec file" ...]

That is followed by this:

        0x00007ffff7dda1c8 - 0x00007ffff7dda1ec is .note.gnu.build-id in
/lib64/ld-linux-x86-64.so.2
        0x00007ffff7dda1f0 - 0x00007ffff7dda2a8 is .hash in
/lib64/ld-linux-x86-64.so.2
        blah in /lib64/blah
        blah in /lib64/blah

Why not instead print the file name once, like we do for "Local exec file".
Then the user doesn't have to keep reading "in blah" over and over.

-- 
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]