From: Roberto Viola <r.viola@elcoelettronica.it>
To: gdb@sourceware.org
Subject: Re: Shared libraries issue
Date: Tue, 09 Oct 2012 07:50:00 -0000 [thread overview]
Message-ID: <1349768208.14797.181.camel@localhost.localdomain> (raw)
In-Reply-To: <1349264817.14797.151.camel@localhost.localdomain>
Probably i've found something:
In gcc on arm, when i ask for shared loaded libraries ("share") it calls
function solib.c:info_sharedlibrary_command with full support for solib
(and it works fine).
Instead, when i ask for the same command on gdb on windows and gdbserver
on arm, it passes the command "qXfer:libraries:read:" that doesn't
manage any solib, only dlls! And the dlls list is obviously empty.
Did i miss something?
On Wed, 2012-10-03 at 13:46 +0200, Roberto Viola wrote:
> Hi,
> it's my first time here, so be gently :)
>
> I'm working on ARM system with gdb 7.1. I'm using this tool to debug an
> application composed by several shared libraries.
>
> If I debug this application on the ARM side, with gdb 7.1 i can see the
> shared loaded libraries (digiting "share"). Perfect!
>
> I'm trying to do the same thing remotelly with gdb for arm on windows
> host and gdbserver on ARM.
>
> So i have:
> 1) gdb on windows for arm v.7.4.1 (i've tried 7.3.1 too)
> 2) gdbserver on arm v.7.1
>
> On Windows i can debug everything flawless except for the shared
> libraries: infact, when i tried to digit "share" it says there isn't any
> shared loaded libraries. I'm absolutely sure that at least one library
> has loaded (on arm side the same situation works fine).
>
> Any idea?
>
> Thanks in advance
> Roberto Viola
>
--
Elco Elettronica Snc
Via Costituzione, 50
42015 - Correggio (RE) - Italy Tel: +39 0522 691024
Tel: +39 0522 691753
Fax: +39 0522 691322
Mail: r.viola@elcoelettronica.it
prev parent reply other threads:[~2012-10-09 7:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 12:00 Roberto Viola
2012-10-09 7:50 ` Roberto Viola [this message]
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=1349768208.14797.181.camel@localhost.localdomain \
--to=r.viola@elcoelettronica.it \
--cc=gdb@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).