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

Thanks, buddies, any way, now I'm clear about the "info shared" command :-)

And "info files", "readelf" are more or less the same, and can provide
more infomation than "info shared".

Regards,
Eric

2006/8/30, Daniel Jacobowitz <drow@false.org>:
> On Wed, Aug 30, 2006 at 01:21:53PM +0800, chen free wrote:
> > So you mean in "0x00002aaaaabd6910  0x00002aaaaabf1e58  Yes
> > /lib/libreadline.so.5" it's the real address of code (.text) segment?
>
> The .text section, not segment.
>
> > Are the "info files" reported the same result as "readelf" or "info shared"?
>
> Sort of.  I don't know what you're asking.
>
> --
> Daniel Jacobowitz
> CodeSourcery
>


  reply	other threads:[~2006-08-30 13:24 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
2006-08-30 12:39             ` Daniel Jacobowitz
2006-08-30 13:24               ` chen free [this message]
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=e55f4e5f0608300624m7d0f8dbeu46cc5ad7433dcbcc@mail.gmail.com \
    --to=dits365@gmail.com \
    --cc=drow@false.org \
    --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