Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "chen free" <dits365@gmail.com>
To: "Mark Kettenis" <mark.kettenis@xs4all.nl>, gdb@sources.redhat.com
Subject: Re: What exactly does "info sharedlibrary" command show?
Date: Wed, 30 Aug 2006 05:22:00 -0000	[thread overview]
Message-ID: <e55f4e5f0608292221s20ce1c95oc4a62751a70840d8@mail.gmail.com> (raw)
In-Reply-To: <20060829201206.GA28907@nevyn.them.org>

Hi, Jacobowitz


2006/8/30, Daniel Jacobowitz <drow@false.org>:
> Given this I have a hard time finding anything visually:
>
> 0x00002aaaaabd6910  0x00002aaaaabf1e58  Yes /lib/libreadline.so.5
> 0x00002aaaaad20ef0  0x00002aaaaad43cc8  Yes /usr/lib/libncurses.so.5
> 0x00002aaaaae61dd0  0x00002aaaaaea22b8  Yes /lib/libm.so.6
> 0x00002aaaaafe2000  0x00002aaaaafe2978  Yes /lib/libdl.so.2
> 0x00002aaaab1002d0  0x00002aaaab1e2a10  Yes /lib/libc.so.6
> 0x00002aaaaaaaba80  0x00002aaaaaabc857  Yes /lib64/ld-linux-x86-64.so.2
> 0x00002aaaab50a8e0  0x00002aaaab50dce8  Yes /lib/libthread_db.so.1
>
> I find this much easier:
>
> 0x00002aaaaabd6000  0x00002aaaaabf2000  Yes /lib/libreadline.so.5
> 0x00002aaaaad20000  0x00002aaaaad44000  Yes /usr/lib/libncurses.so.5
> 0x00002aaaaae61000  0x00002aaaaaea3000  Yes /lib/libm.so.6
> 0x00002aaaaafe2000  0x00002aaaaafe3000  Yes /lib/libdl.so.2
> 0x00002aaaab100000  0x00002aaaab1e3000  Yes /lib/libc.so.6
> 0x00002aaaaaaab000  0x00002aaaaaabd000  Yes /lib64/ld-linux-x86-64.so.2
> 0x00002aaaab50a000  0x00002aaaab50e000  Yes /lib/libthread_db.so.1

So you mean in "0x00002aaaaabd6910  0x00002aaaaabf1e58  Yes
/lib/libreadline.so.5" it's the real address of code (.text) segment?

> > True.  Somehow we should make the load address of a shared library
> > available.
>
> Should we use segments in "info files" when available?

Are the "info files" reported the same result as "readelf" or "info shared"?

> --
> Daniel Jacobowitz
> CodeSourcery
>


Regards,
Eric


  parent reply	other threads:[~2006-08-30  5:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-29 12:03 chen free
2006-08-29 12:40 ` Daniel Jacobowitz
2006-08-29 19:15   ` Mark Kettenis
2006-08-29 19:28     ` Daniel Jacobowitz
2006-08-29 20:06       ` Mark Kettenis
2006-08-29 20:12         ` Daniel Jacobowitz
2006-08-29 21:05           ` Steve Eaton
2006-08-29 21:17             ` Daniel Jacobowitz
2006-08-29 21:08           ` Mark Kettenis
2006-08-29 21:24             ` Daniel Jacobowitz
2006-08-30  5:22           ` chen free [this message]
2006-08-30 12:39             ` Daniel Jacobowitz
2006-08-30 13:24               ` chen free
2006-08-29 12:47 ` Frederic RISS
2006-08-29 13:00   ` chen free
2006-08-29 13:20     ` Frederic RISS
2006-08-29 13:36       ` chen free

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e55f4e5f0608292221s20ce1c95oc4a62751a70840d8@mail.gmail.com \
    --to=dits365@gmail.com \
    --cc=gdb@sources.redhat.com \
    --cc=mark.kettenis@xs4all.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox