From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19330 invoked by alias); 30 Aug 2006 05:22:01 -0000 Received: (qmail 19321 invoked by uid 22791); 30 Aug 2006 05:22:00 -0000 X-Spam-Check-By: sourceware.org Received: from py-out-1112.google.com (HELO py-out-1112.google.com) (64.233.166.183) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 30 Aug 2006 05:21:55 +0000 Received: by py-out-1112.google.com with SMTP id x31so99643pye for ; Tue, 29 Aug 2006 22:21:53 -0700 (PDT) Received: by 10.35.134.19 with SMTP id l19mr193996pyn; Tue, 29 Aug 2006 22:21:53 -0700 (PDT) Received: by 10.35.35.4 with HTTP; Tue, 29 Aug 2006 22:21:53 -0700 (PDT) Message-ID: Date: Wed, 30 Aug 2006 05:22:00 -0000 From: "chen free" To: "Mark Kettenis" , gdb@sources.redhat.com Subject: Re: What exactly does "info sharedlibrary" command show? In-Reply-To: <20060829201206.GA28907@nevyn.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20060829123954.GB12955@nevyn.them.org> <200608291914.k7TJEOPY016721@elgar.sibelius.xs4all.nl> <20060829192758.GA27571@nevyn.them.org> <200608292005.k7TK5M2q021703@elgar.sibelius.xs4all.nl> <20060829201206.GA28907@nevyn.them.org> Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-08/txt/msg00234.txt.bz2 Hi, Jacobowitz 2006/8/30, Daniel Jacobowitz : > 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